CVE-2019-14243 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in github.com/mastercactapus/proxyprotocol. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/mastercactapus/proxyprotocol — see the affected versions and patch details below.
mastercactapus proxyprotocol vulnerable to denial of service
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mastercactapus/proxyprotocolReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
headerv2.go in mastercactapus proxyprotocol before 0.0.2, as used in the mastercactapus caddy-proxyprotocol plugin through 0.0.2 for Caddy, allows remote attackers to cause a denial of service (webserver panic and daemon crash) via a crafted HAProxy PROXY v2 request with truncated source/destination address data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mastercactapus/proxyprotocol | all versions | 0.0.2go get github.com/mastercactapus/proxyprotocol@v0.0.2 |
Affected Products
proxyprotocolhaproxyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mastercactapus/proxyprotocol, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mastercactapus/proxyprotocol to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14243 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2019-14243 in your dependencies?
Find it across Go, including transitive dependencies.