dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-54134

HIGH · 8.3 CVSS v4.0 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A publish-access account was compromised for `@solana/web3.js`, a JavaScript library that is commonly used by Solana dapps. This allowed an attacker to publish unauthorized and malicious packages that were modified, allowing them to steal private key material and drain funds from dapps, like bots, that handle private keys directly. This issue should not affect non-custodial wallets, as they generally do not expose private keys during transactions. This is not an issue with the Solana protocol itself, but with a specific JavaScript client library and only appears to affect projects that directly handle private keys and that updated within the window of 3:20pm UTC and 8:25pm UTC on Tuesday, December 3, 2024. These two unauthorized versions (1.95.6 and 1.95.7) were caught within hours and have since been unpublished. All Solana app developers should upgrade to version 1.95.8. Developers that suspect they might be compromised should rotate any suspect authority keys, including multisigs, program authorities, server keypairs, and so on.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A compromised npm publish-access account for @solana/web3.js allowed attackers to publish malicious versions 1.95.6 and 1.95.7 that contained code to steal private keys and drain funds from applications directly handling cryptographic keys.

MitigationImmediately upgrade to version 1.95.8; if the compromised versions (1.95.6 or 1.95.7) were used between 3:20pm and 8:25pm UTC on December 3, 2024, rotate all authority keys including multisigs, program authorities, and server keypairs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of @solana/web3.js
    Run 'npm list @solana/web3.js' or 'yarn list @solana/web3.js' in your project directory to see the installed version
    Affected if The installed version is 1.95.6 or 1.95.7
  2. Inspect package-lock.json or yarn.lock
    Open package-lock.json (npm) or yarn.lock (yarn) and search for '@solana/web3.js' entry to confirm the exact version resolved
    Affected if The lockfile shows version 1.95.6 or 1.95.7 as the installed version
  3. Verify package.json dependency
    Check your project's package.json file under 'dependencies' or 'devDependencies' for the @solana/web3.js entry
    Affected if The declared dependency specifies version 1.95.6 or 1.95.7, or uses a range that resolved to those versions
  4. Check npm/yarn cache timestamps
    Run 'npm view @solana/web3.js versions' or 'npm info @solana/web3.js time' to see version release timestamps
    Affected if The versions 1.95.6 or 1.95.7 appear in the list of installed versions

A user is affected if @solana/web3.js version 1.95.6 or 1.95.7 is installed in their environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade to version 1.95.8; if the compromised versions (1.95.6 or 1.95.7) were used between 3:20pm and 8:25pm UTC on December 3, 2024, rotate all authority keys including multisigs, program authorities, and server keypairs.

Recommended fix High confidence

@solana/web3.js version 1.95.8

  1. Check your project's package.json or package-lock.json for @solana/web3.js version
  2. If version 1.95.6 or 1.95.7 is present, update package.json to specify version 1.95.8
  3. Run 'npm install' or 'npm update @solana/web3.js' to install the fixed version
  4. Verify the installed version is 1.95.8 by running 'npm list @solana/web3.js'
  5. If you believe you updated during the attack window (3:20pm-8:25pm UTC on December 3, 2024), rotate any exposed authority keys including multisigs, program authorities, and server keypairs

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54134 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data