LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28269: Prototype pollution vulnerability in 'field' versions 0.0.1 through 1.0.1 allows attacker to cause a denial...

Prototype pollution vulnerability in 'field' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-28269 affects the npm package `field` in versions 0.0.1 through 1.0.1. It is a prototype pollution issue that can cause denial of service and may lead to remote code execution. Business urgency depends on whether this package processes attacker-controlled data in your applications.

Executive priority

Treat this as high priority when vulnerable `field` versions are present in production server-side applications, especially internet-facing systems. If the package is unused, test-only, or unreachable from untrusted input, urgency is lower but cleanup is still advisable.

Technical view

The issue is reported as prototype pollution in `field`, with affected versions explicitly listed as 0.0.1, 0.1.0, 1.0.0, and 1.0.1. The public record does not provide CVSS, CWE, exploitation details, or a named fixed version in the supplied sources.

Likely exposure

Exposure is most likely in Node.js applications or transitive dependency chains that include vulnerable `field` versions and pass untrusted input into affected code paths.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV. The impact statement includes denial of service and possible remote code execution, but exploitability depends on application usage and input reachability.

Researcher notes

The record is sparse: no CVSS vector, CWE mapping, fixed version, PoC status, or KEV listing is present in the supplied bundle. Analysis should focus on dependency presence, call-path reachability, and whether polluted object properties can affect security decisions or process stability.

Mitigation direction

  • Inventory direct and transitive use of `field` in Node.js projects.
  • Check vendor or package maintainer guidance for a fixed or replacement version.
  • Remove or replace `field` where no maintained fix is available.
  • Restrict untrusted input from reaching vulnerable parsing or assignment paths.
  • Prioritize internet-facing services and privileged server-side runtimes first.

Validation and detection

  • Search dependency lockfiles for `field` versions 0.0.1 through 1.0.1.
  • Confirm whether vulnerable versions are loaded in production builds.
  • Trace whether attacker-controlled data reaches `field` processing paths.
  • Review runtime crash, pollution, or unexpected object-property behavior around affected services.
  • Document findings where the package is transitive but unreachable.
Prepared
Confidence
medium
Sources
4

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-28269 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/afield0.0.1, 0.1.0, 1.0.0, 1.0.1Listed
Weakness

CWE details

No CWE listed

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