Skip to content
Fencer Intel
medium 6.5

CVE-2023-46234 json

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

published 3y ago modified 2mo ago also EUVD-2023-2835 , GHSA-x9w5-v3q2-3rhw

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm browserify-sign 4.2.2
  • browserify browserify-sign 4.2.2
  • node-browserify-sign Debian 12 4.2.1-3+deb12u1
  • node-browserify-sign Debian 14, Debian 13 4.2.2-1

debian advisories DEBIAN-CVE-2023-46234

  • node-browserify-sign Ubuntu 20.04 LTS 4.0.4-2ubuntu0.20.04.1
  • node-browserify-sign Ubuntu 22.04 LTS 4.2.1-2ubuntu0.1
  • node-browserify-sign Ubuntu Pro 18.04 LTS 4.0.4-2ubuntu0.18.04.1~esm1

ubuntu advisories UBUNTU-CVE-2023-46234

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • velociraptor openSUSE Tumbleweed 0.7.0.4.git142.862ef23-1.1

opensuse advisories openSUSE-SU-2025:14663-1

  • reaper CBL-Mariner 2.0 3.1.1-9

azure linux advisories AZL-31719

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2023-46234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-46234 updated cvss 7.5

browserify-sign: upper bound check issue in dsaVerify leads to a signature forgery attack

  • Red Hat OpenShift Pipelines openshift-pipelines/pipelines-hub-ui-rhel8, openshift-pipelines/pipelines-hub-api-rhel8, openshift-pipelines/pipelines-hub-db-migration-rhel8
    affected: workaround, no fix available “No current mitigation is yet available for this flaw.”
  • Red Hat OpenShift Serverless browserify-sign Red Hat OpenShift Service Mesh 2 openshift-service-mesh/kiali-rhel8 Red Hat 3scale API Management Platform 2 browserify-sign
    affected: workaround, no fix planned “No current mitigation is yet available for this flaw.”
  • Red Hat Certification for Red Hat Enterprise Linux 7 redhat-certification
    affected: workaround, no fix available “No current mitigation is yet available for this flaw.”
  • Red Hat Enterprise Linux 6 firefox Red Hat Enterprise Linux 7 firefox
    affected: workaround, no fix planned “No current mitigation is yet available for this flaw.”
  • Red Hat Fuse 7 browserify-sign
    affected: workaround, no fix available “No current mitigation is yet available for this flaw.”
  • Red Hat JBoss Data Grid 7 browserify-sign Red Hat OpenShift Container Platform 3.11 openshift3/ose-console Red Hat OpenShift Container Platform 4 openshift4/ose-console Red Hat Openshift Container Storage 4 ocs4/mcg-core-rhel8
    affected: workaround, no fix planned “No current mitigation is yet available for this flaw.”
  • Red Hat OpenShift Data Science (RHODS) rhods/odh-dashboard-rhel8 Red Hat OpenShift Dev Spaces devspaces/traefik-rhel8, devspaces/dashboard-rhel8 Red Hat OpenShift distributed tracing 2 rhosdt/jaeger-agent-rhel8, rhosdt/jaeger-query-rhel8, rhosdt/jaeger-ingester-rhel8, rhosdt/jaeger-collector-rhel8, rhosdt/jaeger-all-in-one-rhel8, rhosdt/jaeger-es-rollover-rhel8, +1 more
    affected: workaround, no fix available “No current mitigation is yet available for this flaw.”
  • Red Hat Quay 3 quay/quay-rhel8
    affected: workaround, no fix planned “No current mitigation is yet available for this flaw.”
show 2 more
  • Red Hat Developer Hub 1.2 for RHEL 9 rhdh/rhdh-hub-rhel9 1.2-154
    fixed: vendor fix “No current mitigation is yet available for this flaw.” RHBA-2024:10184
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/console-rhel8 Red Hat Ansible Automation Platform 2 aap-azure-ui Red Hat build of Apicurio Registry 2 browserify-sign Red Hat Decision Manager 7 browserify-sign Red Hat Developer Hub 1.2 for RHEL 9 rhdh/rhdh-rhel9-operator 1.2-148, rhdh/rhdh-operator-bundle 1.2-147
    +9 more products
    Red Hat Enterprise Linux 8 pcs, grafana, mozjs60, pcs-snmp, grafana-loki, grafana-mssql, +11 more Red Hat Enterprise Linux 9 gjs, pcs, polkit, pcs-snmp, polkit-libs Red Hat Integration Camel K 1 browserify-sign Red Hat JBoss Enterprise Application Platform 7 browserify-sign Red Hat JBoss Enterprise Application Platform Expansion Pack browserify-sign Red Hat Openshift Data Foundation 4 odf4/mcg-core-rhel8 Red Hat OpenShift GitOps openshift-gitops-1/argo-rollouts-rhel8 Red Hat Process Automation 7 browserify-sign Red Hat Satellite 6 rubygem-rabl, nodejs-webpack, tfm-rubygem-rabl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm browserify-sign
>=2.6.0, <4.2.2
4.2.2

Affected products

  • browserify browserify-sign

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of browserify/browserify-sign published their own advisory on GitHub. Reviewed sources take precedence over it.