Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-24771

node-forge: Signature verification leniency in checking `digestAlgorithm` structure can lead to signature forgery

Overview

Published
18 Mar 2022
Modified
17 Jun 2026
High CVE
1 Registry packages
4 OS packages
2 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weakness: CWE-347

Affected packages · 1

Packages affected by CVE-2022-24771
EcosystemPackageVulnerableFixed in
npm node-forge <1.3.0 1.3.0

Open a package to see all its vulnerabilities.

Operating systems · 4 fixes

Red Hat 1 release · 2 packages

affected 1 wont fix 1
servicemesh-prometheus pcs
Red Hat fixes for CVE-2022-24771
ReleasePackageFixed in
8 servicemesh-prometheus affected
8 pcs +1 wont fix

debian 2 releases · 1 package

fixed 2
node-node-forge
debian fixes for CVE-2022-24771
ReleasePackageFixed in
10 node-node-forge 0.8.1~dfsg-1+deb10u1
11 node-node-forge 0.10.0~dfsg-3+deb11u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.