LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28503: Prototype Pollution

The package copy-props before 2.0.5 are vulnerable to Prototype Pollution via the main functionality.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-28503 affects the JavaScript package copy-props before 2.0.5. It can allow prototype pollution, where unsafe object property copying changes shared object behavior. Business risk depends on whether the package processes attacker-controlled data in applications or build/runtime paths.

Executive priority

Treat as a high-priority dependency remediation where copy-props is present in production or internet-facing systems. It is not marked as known exploited in the provided sources, so prioritize based on asset exposure and upgrade feasibility.

Technical view

The issue is prototype pollution in copy-props main functionality before 2.0.5. The supplied CVSS 3.1 score is 7.3, with network attack vector, low complexity, no privileges, and no user interaction. Expected impact is limited confidentiality, integrity, and availability loss.

Likely exposure

Exposure is most likely in applications or dependency trees using copy-props before 2.0.5, including transitive usage. Check JavaScript dependency manifests, lockfiles, SBOMs, and any WebJars inventory for copy-props references.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS temporal data indicates proof-of-concept maturity and an official remediation, but no weaponized exploitation details are provided.

Researcher notes

Evidence identifies the vulnerable package and fixed threshold but does not provide detailed affected call patterns. Validate reachability before overstating impact, especially for build-only or unused transitive dependencies.

Mitigation direction

  • Upgrade copy-props to version 2.0.5 or later.
  • Regenerate and review lockfiles after dependency updates.
  • Check vendor advisories for npm and WebJars packaging guidance.
  • Prioritize services that process untrusted object-shaped input.
  • Deploy after normal regression testing confirms application behavior.

Validation and detection

  • Search SBOMs and lockfiles for copy-props versions before 2.0.5.
  • Confirm transitive dependency resolution no longer selects vulnerable versions.
  • Review reachable code paths that pass untrusted data into property-copy helpers.
  • Run existing unit and integration tests after dependency remediation.
  • Document any temporary exception with owner and review date.
Prepared
Confidence
high
Sources
5

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-28503 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.3 (3.1)
Known Exploited
No
Published

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

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
4Source 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.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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/acopy-propsunspecifiedListed
Weakness

CWE details

No CWE listed

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