CVE-2019-12158
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 GetExtension heap-based buffer overflow via a long extension.
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 · moderate confidenceGoHTTP through version 2017-07-25 contains a heap-based buffer overflow vulnerability in the GetExtension function. The overflow occurs when processing an excessively long file extension, allowing potential memory corruption and possible remote code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify if GoHTTP is installedCheck for GoHTTP binary or service: look for files named 'gohttp', 'GoHTTP', or a server listening on common GoHTTP ports (typically 8080, 8888). Use commands like 'which gohttp', 'ps aux | grep -i gohttp', or 'netstat -anp | grep -E "8080|8888"'.Affected if GoHTTP binary exists or a service on ports 8080/8888 is running and responds to requests.
-
Determine GoHTTP versionRun 'gohttp -version' or check the binary's metadata. If running as a service, check process info or startup logs for the build date. The affected version is <= 2017-07-25.Affected if The version date is 2017-07-25 or earlier, or the version cannot be determined (indicating an old build).
-
Check if file upload/extension handling is enabledReview GoHTTP configuration files for settings related to static file serving, file uploads, or the GetExtension function usage. Look for flags like '-serve', '-upload', or similar file-handling options in startup scripts or config files.Affected if Static file serving or file upload functionality is enabled, allowing user-supplied filenames to reach the GetExtension function.
-
Verify network exposureCheck if GoHTTP is exposed to untrusted network paths. Review firewall rules, reverse proxy configurations, or port bindings. Determine if external users can send requests with custom file extensions.Affected if GoHTTP is accessible externally without input validation proxies in front of it.
You are affected if GoHTTP version 2017-07-25 or earlier is running with file extension handling enabled and accessible to users who can supply long extension strings.
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 patch for this vulnerability. If upgrading is not feasible, implement input validation to restrict extension length before passing to GetExtension.
- 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-12158 — 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-12158 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