net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applica
Noroxi assessment
Priority: Plan (action score 42/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.3% (FIRST EPSS); higher than 94.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: golang-1.11 (Debian:10) 1.11.6-1+deb10u1; stdlib (Go) 1.12.8, 1.11.13; go1.11 (openSUSE:Leap 15.0) 1.11.13-lp151.2.9.1.
Add it to your regular patch cycle. Upgrade to golang-1.11 (Debian:10) 1.11.6-1+deb10u1; stdlib (Go) 1.12.8, 1.11.13; go1.11 (openSUSE:Leap 15.0) 1.11.13-lp151.2.9.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications. This is related to a Host field with a suffix appearing in neither Hostname() nor Port(), and is related to a non-numeric port number. For example, an attacker can compose a crafted javascript:// URL that results in a hostname of google.com.
- Published
- Aug 13, 2019
- Updated
- Jun 16, 2026
- EPSS
- 8.3% · 94th percentile
- CWE
- —
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 8.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- golang gobefore 1.11.13
- golang go1.12.0 and later · before 1.12.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | golang-1.11 | before 1.11.6-1+deb10u1 | 1.11.6-1+deb10u1 |
| Go | stdlib | from 1.12.0-0 · before 1.12.8 | 1.12.8 |
| Go | stdlib | before 1.11.13 | 1.11.13 |
| openSUSE:Leap 15.0 | go1.11 | before 1.11.13-lp151.2.9.1 | 1.11.13-lp151.2.9.1 |
| openSUSE:Leap 15.0 | go1.12 | before 1.12.9-lp151.2.13.1 | 1.12.9-lp151.2.13.1 |
| openSUSE:Leap 15.1 | go1.12 | before 1.12.9-lp151.2.9.1 | 1.12.9-lp151.2.9.1 |
| openSUSE:Leap 15.1 | go1.12 | before 1.12.9-lp151.2.21.1 | 1.12.9-lp151.2.21.1 |
| openSUSE:Leap 15.1 | go1.12 | before 1.12.9-lp151.2.17.1 | 1.12.9-lp151.2.17.1 |
| openSUSE:Tumbleweed | go1.11 | before 1.11.13-10.5 | 1.11.13-10.5 |
| openSUSE:Tumbleweed | go1.12 | before 1.12.17-4.8 | 1.12.17-4.8 |
| Red Hat:devtools:2019 | go-toolset-1.12 | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-build | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-bin | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-docs | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-misc | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-race | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-src | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-golang-tests | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:devtools:2019 | go-toolset-1.12-runtime | before 0:1.12.8-2.el7 | 0:1.12.8-2.el7 |
| Red Hat:enterprise_linux:8::appstream | go-toolset | before 0:1.12.8-1.module+el8.1.0+4089+be929cf8 | 0:1.12.8-1.module+el8.1.0+4089+be929cf8 |
| Red Hat:enterprise_linux:8::appstream | golang | before 0:1.12.8-2.module+el8.1.0+4089+be929cf8 | 0:1.12.8-2.module+el8.1.0+4089+be929cf8 |
| Red Hat:enterprise_linux:8::appstream | golang-bin | before 0:1.12.8-2.module+el8.1.0+4089+be929cf8 | 0:1.12.8-2.module+el8.1.0+4089+be929cf8 |
| Red Hat:enterprise_linux:8::appstream | golang-docs | before 0:1.12.8-2.module+el8.1.0+4089+be929cf8 | 0:1.12.8-2.module+el8.1.0+4089+be929cf8 |
+4
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only 54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH42Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-9741Mar 13, 2019 · An issue was discovered in net/http in Go 1.11.5.25Monitor
- ← EarlierCVE-2019-11888May 13, 2019 · Go through 1.12.5 on Windows mishandles process creation with a nil environment in conjunction with a non-nil token, which allows attackers 40Plan
- Later →CVE-2019-16276Sep 30, 2019 · Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling.32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:golang-1.11 | 1.11.6-1+deb10u1 · Debian:10 | Package registry (OSV) |
| Go:stdlib | 1.11.13 | Package registry (OSV) |
| Go:stdlib | 1.12.8 | Package registry (OSV) |
| opensuse:go1.11 | 1.11.13-lp151.2.9.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:go1.12 | 1.12.9-lp151.2.9.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:go-toolset | 0:1.12.8-1.module+el8.1.0+4089+be929cf8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:go-toolset-1.12 | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-build | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-bin | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-docs | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-misc | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-race | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-src | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-golang-tests | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:go-toolset-1.12-runtime | 0:1.12.8-2.el7 · Red Hat:devtools:2019 | Package registry (OSV) |
| red hat:golang | 0:1.12.8-2.module+el8.1.0+4089+be929cf8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00002.html
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00011.html
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00021.html
- lists.opensuse.org/opensuse-security-announce/2019-09/msg00038.html
- access.redhat.com/errata/RHSA-2019:3433
- groups.google.com/forum/#%21topic/golang-announce/0uuMm1BwpHE
- groups.google.com/forum/#%21topic/golang-announce/65QixT3tcmg
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4BBP27PZGSY6OP6D26E5FW4GZKBFHNU7/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LYO6E3H34C346D2E443GLXK7OK6KIYIQ/
- seclists.org/bugtraq/2019/Aug/31
- www.debian.org/security/2019/dsa-4503
Vendor advisories and official records. Exploit/PoC links are deliberately left out.