Cyber Resilience

CVE-2020-7774

Y18N Project Y18N ≤ 3.2.2

Public PoCHigh EPSS
Published
17 November 2020
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.69 99.3th percentile
Risk Priority 80 floored blend · peak EPSS

Summary

CVE-2020-7774 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Y18N Project Y18N. Its CVSS base score is 7.3 (High).

Operationally, ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.

CWE(s)

Related Threats

CVEs Like This One

CVE-2019-0230Same vendor: Oracle
CVE-2023-21986Same product: Oracle Graalvm
CVE-2024-54156Shared CWE-1321
CVE-2026-48819Shared CWE-1321
CVE-2026-34626Shared CWE-1321
CVE-2024-52441Shared CWE-1321
CVE-2026-59876Shared CWE-1321
CVE-2023-26121Shared CWE-1321
CVE-2024-57071Shared CWE-1321
CVE-2024-57064Shared CWE-1321

Affected Assets

y18n project
y18n
4.0.0 · ≤ 3.2.2 · 5.0.0 — 5.0.5
oracle
graalvm
19.3.5, 20.3.1.2, 21.0.0.2
siemens
sinec infrastructure network services
≤ 1.0.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development catches prototype-pollution flaws before release.

prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References