CVE-2019-12159
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGoHTTP through 2017-07-25 has a stack-based buffer over-read in the scan function (when called from getRequestType) via a long URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGoHTTP through 2017-07-25 contains a stack-based buffer over-read vulnerability in the scan function (when invoked from getRequestType). The vulnerability is triggered by sending a specially crafted long URL, allowing an attacker to read memory beyond allocated buffer boundaries on the stack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2017-07-25CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine if GoHTTP is installedCheck for the gohttp binary on the system using 'which gohttp' or by listing running processes with 'ps aux | grep -i gohttp'Affected if The gohttp binary exists or is running as a process on the system
-
Identify the installed GoHTTP versionRun 'gohttp -v' or 'gohttp --version' to display version information. If not available, check the binary's modification timestamp using 'ls -la $(which gohttp)'Affected if The version date is on or before 2017-07-25, or the binary was created/modified on or before that date with no version flag available
-
Verify if GoHTTP is exposed to network requestsCheck if the GoHTTP service is listening on a network port using 'netstat -tulpn | grep gohttp' or 'ss -tulpn | grep gohttp'Affected if GoHTTP is bound to a network interface (0.0.0.0 or specific IP) and accepting HTTP connections
-
Assess exposure to long URL requestsReview any reverse proxy, firewall, or WAF configuration in front of GoHTTP to determine if long URL requests can reach the serviceAffected if No URL length filtering exists upstream and the service directly accepts client requests
The environment is affected if GoHTTP is installed with a version dated 2017-07-25 or earlier and is directly accessible to accept network requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade GoHTTP to a version released after 2017-07-25 that contains the fix. If upgrading is not feasible, implement URL length constraints at a reverse proxy or WAF layer to reject abnormally long requests.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12159 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data