Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

browserify-sign · Vulnerability

CVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 CVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by browserify-sign 4.2.2KEV status unknown

cve-program · CVE-2023-46234

Published

browserify-sign is a package to duplicate the functionality of node's crypto public key functions, much of this is based on Fedor Indutny's work on indutny/tls.js. An upper bound check issue in `dsaVerify` function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. This issue has been patched in version 4.2.2.

Read the publisher's advisory

euvd · EUVD-2023-2835

Published

browserify-sign is a package to duplicate the functionality of node's crypto public key functions, much of this is based on Fedor Indutny's work on indutny/tls.js. An upper bound check issue in `dsaVerify` function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. This issue has been patched in version 4.2.2.

Read the publisher's advisory

nvd · CVE-2023-46234

Published

browserify-sign is a package to duplicate the functionality of node's crypto public key functions, much of this is based on Fedor Indutny's work on indutny/tls.js. An upper bound check issue in `dsaVerify` function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. This issue has been patched in version 4.2.2.

Read the publisher's advisory

osv · GHSA-x9w5-v3q2-3rhw

Published

### Summary An upper bound check issue in `dsaVerify` function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. ### Details In `dsaVerify` function, it checks whether the value of the signature is legal by calling function `checkValue`, namely, whether `r` and `s` are both in the interval `[1, q - 1]`. However, the second line of the `checkValue` function wrongly checks the upper bound of the passed parameters, since the value of `b.cmp(q)` can only be `0`, `1` and `-1`, and it can never be greater than `q`. In this way, although the values of `s` cannot be `0`, an attacker can achieve the same effect as zero by setting its value to `q`, and then send `(r, s) = (1, q)` to pass the verification of any public key. ### Impact All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. ### Fix PR: Since the temporary private fork was deleted, here's a webarchive of the PR discussion and diff pages: [PR webarchive.zip](https://github.com/browserify/browserify-sign/files/13172957/PR.webarchive.zip)

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-46234

Published

browserify-sign

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "browserify",
                    "product": "browserify-sign",
                    "versions": [
                        {
                            "version": ">= 2.6.0, <= 4.2.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2023-2835

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 26, 2023, 2:31:35 PM

dateUpdated: Feb 13, 2025, 5:14:23 PM

7 related source bulletins · separate from aliases

RHSA-2023:6180: Red Hat Security Advisory: Red Hat OpenShift distributed tracing 2.9.0 containers security update

CVE-2023-46234

WID-SEC-W-2023-2782: Red Hat OpenShift distributed tracing: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

CVE-2023-46234

RHBA-2024:10184: Red Hat Bug Fix Advisory: Red Hat Developer Hub 1.2.5 bugfix release

CVE-2023-46234 · CVE-2024-43799

NCSC-2024-0466: Kwetsbaarheden verholpen in Atlassian producten

CVE-2022-38900 · CVE-2023-46234 · CVE-2023-52428 · CVE-2024-4068 · CVE-2024-21697 · CVE-2024-24549 · CVE-2024-30172 · CVE-2024-34750 · CVE-2024-38286 · CVE-2024-38816 · CVE-2024-45801 · CVE-2024-47561

msrc_CVE-2023-46234: browserify-sign vulnerable via an upper bound check issue in `dsaVerify` that leads to a signature forgery attack

CVE-2023-46234

WID-SEC-W-2024-3508: Atlassian Confluence: Mehrere Schwachstellen

CVE-2022-38900 · CVE-2023-52428 · CVE-2024-24549 · CVE-2024-30172 · CVE-2024-4068 · CVE-2023-46234 · CVE-2024-38816

openSUSE-SU-2025:14663-1: velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media

CVE-2023-1732 · CVE-2023-44270 · CVE-2023-45133 · CVE-2023-45683 · CVE-2023-46234 · CVE-2024-21538 · CVE-2024-23331 · CVE-2024-24786 · CVE-2024-28180 · CVE-2024-31207 · CVE-2024-37298 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-42459 · CVE-2024-42460 · CVE-2024-42461 · CVE-2024-45296 · CVE-2024-45338 · CVE-2024-45811 · CVE-2024-45812 · CVE-2024-47068 · CVE-2024-47875 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-51744 · CVE-2024-55565 · CVE-2024-6104

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-46234

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-347

Original publisher date fields

published: 2023-10-26T15:15:09.087

lastModified: 2026-06-17T06:30:28.270

3 source CPE criteria · context only
  • cpe:2.3:a:browserify:browserify-sign:*:*:*:*:*:node.js:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-x9w5-v3q2-3rhw

Published

browserify-sign

npm

SEMVER · introduced 2.6.0 → fixed 4.2.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current