Google Go up to 1.12.9/1.13.0 HTTP Request request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Go up to 1.12.9/1.13.0. This vulnerability affects unknown code. The manipulation as part of HTTP Request leads to request smuggling. This vulnerability is traded as CVE-2019-16276. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Google Go up to 1.12.9/1.13.0 (Programming Language Software). It has been rated as critical. This issue affects some unknown functionality. The manipulation as part of a HTTP Request leads to a request smuggling vulnerability. Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling.
The weakness was shared 09/30/2019 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2019-16276 since 09/12/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 235604 (Tenable Sensor Proxy < 1.2.0 Multiple Vulnerabilities (TNS-2025-08)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.12.10 or 1.13.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (235604). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 1.0
- 1.1
- 1.2
- 1.3
- 1.4
- 1.5
- 1.6
- 1.7
- 1.8
- 1.9
- 1.10
- 1.11
- 1.12
- 1.12.0
- 1.12.1
- 1.12.2
- 1.12.3
- 1.12.4
- 1.12.5
- 1.12.6
- 1.12.7
- 1.12.8
- 1.12.9
- 1.13.0
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Request smugglingCWE: CWE-444
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 235604
Nessus Name: Tenable Sensor Proxy < 1.2.0 Multiple Vulnerabilities (TNS-2025-08)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Go 1.12.10/1.13.1
Timeline
09/12/2019 🔍09/30/2019 🔍
10/01/2019 🔍
05/09/2025 🔍
Sources
Vendor: google.comAdvisory: RHSA-2020:0101
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-16276 (🔍)
GCVE (CVE): GCVE-0-2019-16276
GCVE (VulDB): GCVE-100-142739
Entry
Created: 10/01/2019 12:32Updated: 05/09/2025 05:18
Changes: 10/01/2019 12:32 (57), 09/17/2020 10:15 (1), 12/29/2023 08:07 (4), 05/09/2025 05:18 (20)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.