Security readout for executives and security teams
Plain-English summary
A JavaScript cryptography library used for secp256k1 ECDSA signatures accepted invalid signature values. In versions before 1.1.0, this could let an attacker forge a signature in systems that trust this package for authorization, transaction, or message integrity checks. Business impact depends on where the package validates security decisions.
Executive priority
Prioritize remediation for systems using this library in authentication, financial, blockchain, signing, or integrity workflows. Deprioritize only after confirming the package is absent or not used for signature verification. No source in the bundle confirms active exploitation.
Technical view
secp256k1-js before 1.1.0 implemented ECDSA without required r and s validation, mapped to CWE-347. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, reflecting unauthenticated network-reachable integrity impact with no confidentiality or availability impact stated.
Likely exposure
Exposure is likely limited to Node.js applications that depend on @lionello/secp256k1-js or secp256k1-js versions before 1.1.0 and use it to verify ECDSA signatures for trust decisions. The CVE source bundle does not identify downstream products or CPEs.
Exploitation context
The sources describe signature forgery, but the bundle provides no KEV listing and no cited evidence of active exploitation. Treat exploitability as plausible in vulnerable verification paths, not as confirmed real-world exploitation.
Researcher notes
The core issue is missing validation of ECDSA r and s values before version 1.1.0. Public metadata lists CWE-347 and high integrity impact. The affected CPE data is not populated, so dependency-level investigation is required.
Mitigation direction
- Inventory Node.js dependencies for @lionello/secp256k1-js or secp256k1-js before 1.1.0.
- Upgrade affected package usage to version 1.1.0 or later where compatible.
- Prioritize applications where signatures authorize money movement, account access, or integrity-critical messages.
- Check vendor or maintainer guidance for any additional remediation details.
Validation and detection
- Review lockfiles and dependency manifests for vulnerable secp256k1-js package versions.
- Confirm deployed artifacts use the remediated package version, not only source manifests.
- Identify code paths where ECDSA verification results grant trust or authorization.
- Add regression tests that reject invalid r and s signature values.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-41340 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lionello/secp256k1-js/issues/11CVE reference · x_refsource_MISC
- https://github.com/lionello/secp256k1-js/commit/302800f0370b42e360a33774bb808274ac729c2eCVE reference · x_refsource_MISC
- https://github.com/lionello/secp256k1-js/compare/1.0.1...1.1.0CVE reference · x_refsource_MISC
- https://www.npmjs.com/package/%40lionello/secp256k1-jsCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.