p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in node-node-forge · Seite 2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für node-node-forge: 15. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 27

  1. CVE-2025-66030

    Mittel · CVSS 6.3EPSS 0,33%Keine Korrektur veröffentlicht

    node-forge ASN.1 OID Integer Truncation

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

    Veröffentlicht Aktualisiert
  2. CVE-2025-66031

    Hoch · CVSS 8.7EPSS 0,45%Keine Korrektur veröffentlicht

    node-forge ASN.1 Unbounded Recursion

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

    Veröffentlicht Aktualisiert
  3. CVE-2025-12816

    Hoch · CVSS 8.6EPSS 0,58%Keine Korrektur veröffentlicht

    CVE-2025-12816

    An interpretation-conflict (CWE-436) vulnerability in node-forge versions 1.3.1 and earlier enables unauthenticated attackers to craft ASN.1 structures to desynchronize schema validations, yielding a semantic divergence that may bypass downstream cryptographic verifications and security decisions.

    Veröffentlicht Aktualisiert
  4. CVE-2022-24772

    Hoch · CVSS 7.5EPSS 1,11%Keine Korrektur veröffentlicht

    Improper Verification of Cryptographic Signature in `node-forge`

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a `DigestInfo` ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.

    Veröffentlicht Aktualisiert
  5. CVE-2022-24773

    Mittel · CVSS 5.3EPSS 0,96%Keine Korrektur veröffentlicht

    Improper Verification of Cryptographic Signature in `node-forge`

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not properly check `DigestInfo` for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.

    Veröffentlicht Aktualisiert
  6. CVE-2022-24771

    Hoch · CVSS 7.5EPSS 0,78%Keine Korrektur veröffentlicht

    Improper Verification of Cryptographic Signature in node-forge

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →