CVE Intelligence
High Injection exploit reference

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.

Published Aug 30, 2020 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: snyk

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 3.1% (30-day exploitation probability)+13
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
3.11%
ahead of 88% of scored CVEs · Oct 14, 2026
Affects
Joyent
Json and 4 more
CVSS base
7.2
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Joyent Json, Oracle Commerce Guided Search, Oracle Financial Services Crime And Compliance Management Studio…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Joyent Json < 10.0.0 Vulnerable NIST National Vulnerability Database
Oracle Commerce Guided Search version 11.3.2 Vulnerable NIST National Vulnerability Database
Oracle Financial Services Crime And Compliance Management Studio version 8.0.8.2.0version 8.0.8.3.0 Vulnerable NIST National Vulnerability Database
Oracle Financial Services Regulatory Reporting With Agilereporter version 8.0.9.6.3 Vulnerable NIST National Vulnerability Database
Oracle Timesten In-memory Database < 21.1.1.1.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.2 CVSS 3.1 High 1.2 5.9 report@snyk.io via NIST National Vulnerability Database
7.2 CVSS 3.1 High 1.2 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.2 CVSS 3.1 High — — snyk via CVE Program (cve.org) e CISA ADP
6.5 CVSS 2.0 Medium 8.0 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.11%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.2
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2020
  • CVE published
    Aug 30, 2020 · snyk

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

22 on the record

Elsewhere on this site

Joyent
every CVE for this vendor
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • CVE-2022-22971 Allocation of Resources Without Limits or Throttling in Vmware Spring Framework May 12, 2022
  • CVE-2022-22970 Denial of service in Spring Framework May 12, 2022
  • CVE-2022-22947 VMware Spring Cloud Gateway Code Injection Vulnerability KEV Mar 3, 2022
  • CVE-2022-23437 Infinite loop within Apache XercesJ xml parser Jan 24, 2022
  • CVE-2021-37137 Uncontrolled Resource Consumption in Netty Oct 19, 2021
  • CVE-2021-37136 Uncontrolled Resource Consumption in Netty Oct 19, 2021

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-7712 is "Command Injection", rated High. It affects Json (Joyent); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 3.11% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.