Skip to content

Update dependency node-forge to 1.0.0 [SECURITY] - abandoned#36

Open
renovate[bot] wants to merge 2 commits intomasterfrom
renovate/npm-node-forge-vulnerability
Open

Update dependency node-forge to 1.0.0 [SECURITY] - abandoned#36
renovate[bot] wants to merge 2 commits intomasterfrom
renovate/npm-node-forge-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 11, 2021

Mend Renovate

This PR contains the following updates:

Package Change
node-forge 1.2.1 -> 1.3.0

GitHub Vulnerability Alerts

CVE-2022-24771

Impact

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.

Patches

The issue has been addressed in node-forge 1.3.0.

References

For more information, please see
"Bleichenbacher's RSA signature forgery based on implementation error"
by Hal Finney.

For more information

If you have any questions or comments about this advisory:

CVE-2022-24772

Impact

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.

Patches

The issue has been addressed in node-forge 1.3.0.

References

For more information, please see
"Bleichenbacher's RSA signature forgery based on implementation error"
by Hal Finney.

For more information

If you have any questions or comments about this advisory:

CVE-2022-24773

Impact

RSA PKCS#​1 v1.5 signature verification code is not properly checking DigestInfo for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.

Patches

The issue has been addressed in node-forge 1.3.0.

For more information

If you have any questions or comments about this advisory:


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-node-forge-vulnerability branch from e7dcb04 to 146f1bd Compare June 22, 2021 03:31
@renovate
Copy link
Contributor Author

renovate bot commented Jul 2, 2021

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@renovate renovate bot changed the title Update dependency node-forge to 0.10.0 [SECURITY] Update dependency node-forge to 1.0.0 [SECURITY] Jan 10, 2022
@renovate renovate bot changed the title Update dependency node-forge to 1.0.0 [SECURITY] Update dependency node-forge to 1.0.0 [SECURITY] - abandoned Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants