Google Go up to 1.15.11/1.16.4 memory allocation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.4$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Google Go up to 1.15.11/1.16.4. Impacted is an unknown function. Such manipulation leads to memory allocation. This vulnerability is traded as CVE-2021-33198. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Google Go up to 1.15.11/1.16.4 (Programming Language Software). It has been rated as problematic. Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a memory allocation vulnerability. Using CWE to declare the problem leads to CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. Impacted is availability.

The weakness was shared 08/03/2021. The advisory is available at groups.google.com. This vulnerability is handled as CVE-2021-33198. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 211846 (RHEL 8 : container-tools:rhel8 (RHSA-2024:10289)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.15.12 or 1.16.5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (211846). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory allocation
CWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 211846
Nessus Name: RHEL 8 : container-tools:rhel8 (RHSA-2024:10289)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Go 1.15.12/1.16.5

Timelineinfo

05/19/2021 🔍
08/03/2021 +76 days 🔍
08/03/2021 +0 days 🔍
11/26/2024 +1211 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: groups.google.com
Status: Confirmed

CVE: CVE-2021-33198 (🔍)
GCVE (CVE): GCVE-0-2021-33198
GCVE (VulDB): GCVE-100-179954

Entryinfo

Created: 08/03/2021 12:12
Updated: 11/26/2024 18:30
Changes: 08/03/2021 12:12 (38), 08/07/2021 08:35 (2), 11/26/2024 18:30 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!