LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22570: Nullptr Dereference in Protobuf

Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr. We recommend upgrading to version 3.15.0 or greater.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-22570 is a denial-of-service flaw in Google Protobuf. A specially malformed proto symbol can trigger a null pointer dereference while Protobuf builds an error message, potentially crashing the affected process. The documented fix is to upgrade to Protobuf 3.15.0 or later.

Executive priority

Treat this as a moderate availability risk. Patch in the normal vulnerability cycle, but accelerate for shared services, build systems, or platforms where untrusted users can influence proto inputs and a crash would disrupt operations.

Technical view

The issue is CWE-476 in Protobuf symbol parsing. When a null character is present in a proto symbol, parsing can leave the associated file pointer null, followed by an unchecked access to the proto file name during error generation. CVSS 3.1 is 6.5, with high availability impact and no confidentiality or integrity impact.

Likely exposure

Exposure is most relevant where Protobuf tools or libraries parse proto definitions or symbols influenced by lower-privileged users. The source bundle does not define exact affected versions beyond recommending 3.15.0 or greater, so inventory should include OS packages, vendored copies, and application dependencies.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. The impact described is process crash or denial of service, not data theft or code execution. Exploitation requires the vulnerable parsing path to process attacker-influenced proto content or symbols.

Researcher notes

Affected version detail is incomplete in the provided record. The strongest remediation statement is the CVE recommendation to use Protobuf 3.15.0 or later, supplemented by downstream vendor advisories. No source in the bundle supports claims of active exploitation or code execution.

Mitigation direction

  • Upgrade Protobuf to version 3.15.0 or greater.
  • Apply vendor security updates from affected Linux or product vendors.
  • Inventory OS packages, application dependencies, and vendored Protobuf copies.
  • Restrict who can submit proto definitions to build or service pipelines.
  • Check vendor guidance where direct Protobuf versioning is obscured.

Validation and detection

  • Confirm installed Protobuf versions are 3.15.0 or vendor-patched.
  • Review lockfiles, containers, and system packages for older Protobuf.
  • Identify services or jobs that parse user-influenced proto content.
  • Verify patched packages are deployed in Fedora, Debian LTS, Oracle, or NetApp environments if used.
  • Document any unresolved systems pending vendor confirmation.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-22570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
12Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-22570Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google LLCProtobufunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.