LiveActive security incident?Get immediate response
CVE Record

CVE-2020-14968: An issue was discovered in the jsrsasign package before 8.0.17 for Node.js.

An issue was discovered in the jsrsasign package before 8.0.17 for Node.js. Its RSASSA-PSS (RSA-PSS) implementation does not detect signature manipulation/modification by prepending '\0' bytes to a signature (it accepts these modified signatures as valid). An attacker can abuse this behavior in an application by creating multiple valid signatures where only one signature should exist. Also, an attacker might prepend these bytes with the goal of triggering memory corruption issues.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Node.js applications using jsrsasign before 8.0.17 may accept a tampered RSA-PSS signature as valid. This can weaken trust decisions that rely on a single unique signature, such as token, document, or transaction validation. The source bundle does not show active exploitation.

Executive priority

Treat this as a focused cryptographic dependency issue. Prioritize systems where jsrsasign validates signatures for authentication, authorization, or transaction integrity. Broad emergency action is not supported by the provided evidence, but stale vulnerable dependencies should be removed promptly.

Technical view

The flaw is in jsrsasign's RSASSA-PSS verification. Versions before 8.0.17 do not reject signatures altered by adding leading null bytes, so modified signatures can validate when they should fail. The CVE also notes possible attempts to trigger memory corruption, but the provided sources do not confirm exploitability.

Likely exposure

Exposure is likely limited to Node.js systems that depend on jsrsasign before 8.0.17 and verify RSA-PSS signatures for security decisions. Systems not using jsrsasign or not using RSA-PSS verification are not implicated by the provided sources.

Exploitation context

The CVE describes signature manipulation that bypasses expected uniqueness or strict validation. KEV is false, and the source bundle provides no evidence of active exploitation or public weaponization. Impact depends on how the application uses signature validity.

Researcher notes

The key uncertainty is real-world impact: the source bundle identifies acceptance of modified RSA-PSS signatures, but provides no CVSS, CWE, confirmed exploit status, or detailed affected downstream products. Validate exposure by dependency version and actual RSA-PSS use, not package presence alone.

Mitigation direction

  • Inventory Node.js applications and dependencies for jsrsasign versions before 8.0.17.
  • Upgrade jsrsasign to 8.0.17 or later, following vendor release guidance.
  • Review signature-validation workflows that rely on RSA-PSS uniqueness or strict canonical signatures.
  • Check downstream vendor advisories, including NetApp, for product-specific exposure and fixes.

Validation and detection

  • Confirm installed jsrsasign versions from package manifests and lockfiles.
  • Identify code paths using jsrsasign for RSASSA-PSS or RSA-PSS verification.
  • Verify upgraded builds no longer include jsrsasign versions before 8.0.17.
  • Review authentication, token, document, or transaction flows that depend on signature validation.
Prepared
Confidence
medium
Sources
7

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-14968 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
7Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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