Protocol Debt: When an External Input Decides What Your System Executes

Log4Shell, Spring4Shell, Text4Shell and React2Shell share no single technique, but they raise the same review question: what can an external input reach? This preprint proposes "protocol debt", an analytical extension of Cunningham's technical debt, defined as the accumulated gap between the capabilities a component exposes by default and those its consumers believe they have enabled. Patching remains necessary, but a CVE identifies a specific vulnerability; it does not record the trust assumption that joined the layers, nor whether another path preserves it. The paper outlines a verifiable registry of trust assumptions per critical service (accepted input, originator, interpretation, invoked authority, and a test with evidence and review date), a six-step method for teams, and a retrospective example applied to Log4j 2. The thesis is tested against two 2026 cases, PHP2Shell and Java4Shell. Both are memory-safety flaws within a single layer, which the registry does not explain; the paper argues that protocol debt governs blast radius and speed of response, not the existence of each bug. This is an architectural hypothesis with a defined test, not a demonstrated single cause. "Protocol debt" is not a standardized term or a validated metric. The four cases illustrate the thesis and do not prove its prevalence.

Authors

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-11-18
DOI
https://doi.org/10.5281/zenodo.24328302
Primary Topic
Web Application Security Vulnerabilities
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
preprint

Protocol Debt: When an External Input Decides What Your System Executes

Juan Downey
1 links
Zenodo (CERN European Organization for Nuclear Research)
Web Application Security Vulnerabilities
preprint

Protocol Debt: When an External Input Decides What Your System Executes

Juan Downey
preprint en

Abstract

Log4Shell, Spring4Shell, Text4Shell and React2Shell share no single technique, but they raise the same review question: what can an external input reach? This preprint proposes "protocol debt", an analytical extension of Cunningham's technical debt, defined as the accumulated gap between the capabilities a component exposes by default and those its consumers believe they have enabled. Patching remains necessary, but a CVE identifies a specific vulnerability; it does not record the trust assumption that joined the layers, nor whether another path preserves it. The paper outlines a verifiable registry of trust assumptions per critical service (accepted input, originator, interpretation, invoked authority, and a test with evidence and review date), a six-step method for teams, and a retrospective example applied to Log4j 2. The thesis is tested against two 2026 cases, PHP2Shell and Java4Shell. Both are memory-safety flaws within a single layer, which the registry does not explain; the paper argues that protocol debt governs blast radius and speed of response, not the existence of each bug. This is an architectural hypothesis with a defined test, not a demonstrated single cause. "Protocol debt" is not a standardized term or a validated metric. The four cases illustrate the thesis and do not prove its prevalence.

Zenodo (CERN European Organization for Nuclear Research)
Web Application Security Vulnerabilities
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon