LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32292: An issue was discovered in json-c from 20200420 (post 0.14 unreleased code) through 0.15-20200726.

An issue was discovered in json-c from 20200420 (post 0.14 unreleased code) through 0.15-20200726. A stack-buffer-overflow exists in the auxiliary sample program json_parse which is located in the function parseit.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-32292 is a stack buffer overflow in json-c's auxiliary sample program json_parse, not clearly in the core library API. Public data does not provide CVSS, CWE, or active exploitation evidence. Business urgency depends on whether this sample utility is packaged, installed, or reachable in your environment.

Executive priority

Handle through normal vulnerability management unless local inventory shows the sample utility is deployed in sensitive workflows. Prioritize vendor updates for Debian and any NetApp assets, but current evidence does not support emergency response language.

Technical view

The issue affects json-c code from 20200420, after 0.14 unreleased code, through 0.15-20200726. The reported overflow is in json_parse, specifically the parseit function. Debian and NetApp references exist, but the provided bundle does not detail every downstream affected product or exact fixed version.

Likely exposure

Exposure is likely limited to systems that include or use the json-c auxiliary json_parse sample program or downstream packages identified by vendors. The bundle lists affected vendor/product as n/a, so asset-level exposure must be confirmed locally.

Exploitation context

The source bundle does not identify public exploitation, CISA KEV listing, exploit code, or real-world attacks. Treat exploitation status as unconfirmed, not active.

Researcher notes

Key uncertainty is scope: the CVE text points to an auxiliary sample program, while downstream advisories indicate packaged impact may exist. Avoid assuming core library exploitability without confirming how json_parse is built, shipped, or invoked in the target environment.

Mitigation direction

  • Check vendor advisories for fixed json-c packages in your operating system or appliance stack.
  • Apply Debian DSA-5486 updates where Debian-packaged json-c is in scope.
  • Review NetApp advisory guidance for any product-specific exposure or remediation.
  • Remove or restrict unused auxiliary sample utilities where operationally safe.
  • Track vendor guidance because the bundle lacks a universal fixed-version statement.

Validation and detection

  • Inventory systems and containers with json-c packages or bundled json-c source.
  • Check whether the json_parse auxiliary program is installed or used.
  • Compare installed package versions against Debian and vendor advisory guidance.
  • Review software bills of materials for json-c versions in the affected date range.
  • Document systems where vendor impact is unknown pending product guidance.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2021-32292 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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