LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7768: Prototype Pollution

The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.

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

Security readout for executives and security teams

Plain-English summary

This CVE affects Node.js gRPC packages used by applications to define and load service interfaces. Vulnerable versions can allow prototype pollution through loadPackageDefinition, which can destabilize an application and cause denial of service. The sources identify fixed versions, so upgrade priority is straightforward.

Executive priority

Treat this as a high-priority dependency upgrade for internet-facing or business-critical Node.js services using gRPC. It is not presented as actively exploited, but the unauthenticated network CVSS profile and availability impact justify prompt remediation.

Technical view

CVE-2020-7768 covers prototype pollution in grpc before 1.24.4 and @grpc/grpc-js before 1.1.8 via loadPackageDefinition. The provided CVSS 3.1 score is 7.5 high, with network attack vector, low complexity, no privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure is most likely in Node.js services that depend directly or transitively on grpc or @grpc/grpc-js and call loadPackageDefinition. Systems accepting externally influenced package definitions or proto-loading paths deserve closer review.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS temporal vector reports proof-of-concept maturity, but the provided evidence supports denial-of-service risk, not confirmed in-the-wild exploitation.

Researcher notes

The evidence points to prototype pollution in package definition loading rather than confidentiality loss or direct code execution. Validate exact dependency paths, wrapper packages, and whether application-controlled data can influence gRPC package definitions. Avoid assuming exposure from package presence alone.

Mitigation direction

  • Upgrade grpc to 1.24.4 or later where still used.
  • Upgrade @grpc/grpc-js to 1.1.8 or later.
  • Refresh lockfiles and redeploy affected Node.js services.
  • Run software composition analysis to catch transitive vulnerable versions.
  • If upgrading is blocked, check vendor guidance before applying compensating controls.

Validation and detection

  • Inspect package manifests and lockfiles for grpc and @grpc/grpc-js versions.
  • Confirm deployed artifacts contain grpc 1.24.4+ or @grpc/grpc-js 1.1.8+.
  • Search code for loadPackageDefinition usage and review reachable inputs.
  • Verify SCA tooling no longer reports CVE-2020-7768.
  • Review service monitoring for availability anomalies around gRPC package loading.
Prepared
Confidence
high
Sources
6

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-2020-7768 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C

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
6Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C

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/agrpcunspecifiedListed
n/a@grpc/grpc-jsunspecifiedListed
Weakness

CWE details

No CWE listed

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