LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7712: Command Injection

This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.

HighCVSS 7.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-7712 is a command injection issue in the json package before 10.0.0. If an attacker already has high privileges and can influence parseLookup input, they may cause the application host to run unintended commands. Treat this as important where the package exists in operational tooling or backend services.

Executive priority

Prioritize remediation in systems with administrative workflows, automation interfaces, or backend services using this package. The issue is high impact but requires high privileges, so urgency depends on whether the vulnerable code is reachable by privileged users or compromised service accounts.

Technical view

The supplied CVE data describes arbitrary command injection through json.parseLookup before version 10.0.0. CVSS 3.1 is 7.2 high: network reachable, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact. The bundle includes npm and Java WebJars references, but exact downstream exposure must be verified per dependency tree.

Likely exposure

Most likely exposure is applications, build tools, or bundled Java WebJars that depend on the affected json package before 10.0.0 and pass attacker-controlled or tenant-controlled values into parseLookup. Risk is highest where privileged users, admin APIs, or automation accounts can reach the vulnerable path.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector requires high privileges, so this is less likely to be a first-step internet compromise, but it can be serious after account compromise or in admin-facing systems.

Researcher notes

Focus validation on dependency provenance and reachable use of parseLookup. Apache mailing-list references show scanner findings in ZooKeeper and Flink contexts, but the bundle does not prove those projects were directly exploitable. Avoid assuming exploitation or broad product impact without code-path evidence.

Mitigation direction

  • Inventory npm json and related WebJars dependencies across applications and build tooling.
  • Upgrade json to 10.0.0 or later where this dependency is present.
  • Review Snyk and vendor advisories for Java WebJars packaging guidance.
  • Prioritize systems where privileged users can influence parseLookup inputs.
  • If no upgrade path exists, restrict access to affected functionality until vendor guidance is confirmed.

Validation and detection

  • Check SBOMs and lockfiles for json versions before 10.0.0.
  • Search Java dependency reports for org.webjars or org.webjars.npm json artifacts.
  • Confirm whether application code or dependencies call parseLookup with external input.
  • Verify patched builds no longer resolve affected json versions.
  • Document false positives separately where scanners report unrelated json-simple artifacts.
Prepared
Confidence
medium
Sources
9

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-7712 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.2 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ajsonunspecifiedListed
Weakness

CWE details

No CWE listed

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