LiveActive security incident?Get immediate response
CVE Record

CVE-2020-12762: json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated...

json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated by printbuf_memappend.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

json-c, a common JSON parsing library, had an integer overflow that could lead to memory corruption when processing a very large JSON file. Business risk is highest where software parses untrusted JSON. The CVE is high severity, but the supplied sources do not show active exploitation.

Executive priority

Treat as a high-priority patching issue for systems that parse untrusted JSON. It is not currently supported by KEV evidence of active exploitation, so prioritize based on exposure and vendor update availability.

Technical view

CVE-2020-12762 affects json-c through 0.14. The flaw is an integer overflow and out-of-bounds write in printbuf_memappend, classified as CWE-787. CVSS 3.1 is 7.8 with local attack vector and required user interaction. Multiple Linux distributions issued security updates.

Likely exposure

Exposure is likely through operating system packages, embedded products, containers, or applications linking json-c through 0.14. Prioritize systems that parse user-supplied, uploaded, imported, or otherwise untrusted JSON files. The provided affected CPE data is incomplete.

Exploitation context

The supplied CVSS vector requires local access and user interaction. KEV status is false, and the provided sources do not establish active exploitation. The public description confirms a large JSON file can trigger the memory corruption condition.

Researcher notes

The strongest evidence is the CVE description, upstream json-c pull request reference, and multiple distribution advisories. Affected product metadata is sparse, so validation should rely on package inventories, SBOMs, and vendor advisories rather than CPE matching alone.

Mitigation direction

  • Inventory json-c packages and bundled copies across hosts, containers, and appliances.
  • Apply vendor security updates from Linux distributions or upstream json-c guidance.
  • Prioritize systems that process untrusted or externally supplied JSON files.
  • Review downstream product advisories for appliances or embedded software using json-c.
  • If no update exists, restrict untrusted large JSON processing until vendor guidance is available.

Validation and detection

  • Check package managers and SBOMs for json-c versions through 0.14.
  • Confirm installed vendor packages include the CVE-2020-12762 security fix.
  • Identify applications that parse uploaded, imported, or user-controlled JSON files.
  • Review scanner results against Ubuntu, Debian, Fedora, and Gentoo advisories.
  • Document any bundled json-c copies not covered by OS package updates.
Prepared
Confidence
medium
Sources
12

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-787: 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-2020-12762 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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
17Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-12762Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.