CVE-2018-8319: Sensitive Data Exposure in msrcrypto

msrcrypto Updated 02 Oct 2025

Summary

10/09/2018
Yes i
Critical
9.8

CVE-2018-8319: Sensitive Data Exposure in msrcrypto. Affects msrcrypto versions < 1.4.1. Fixed in 1.4.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

msrcrypto is an npm package that provides cryptographic functionality for Microsoft Edge. It includes implementations of various cryptographic algorithms, including Elliptic Curve Cryptography (ECC). ECC is used for secure key exchange and digital signatures. However, versions of msrcrypto prior to 1.4.1 are vulnerable to a sensitive data exposure issue in its ECC implementation.

Vulnerability Detail

The vulnerability in msrcrypto allows an attacker to obtain sensitive information about a server's private ECC key. This can lead to unauthorized access, data theft, and other malicious activities. Additionally, the vulnerability enables attackers to craft invalid ECDSA signatures that can pass as valid, compromising the integrity and authenticity of cryptographic operations. It is important to note that there is no published proof-of-concept for this vulnerability at the moment.

How To Fix

Latest published version: 1.5.8 as of 23 Oct 2026

npm install msrcrypto@1.5.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.4.1

This is the first release that contains the fix.

npm install msrcrypto@1.4.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The vulnerability in msrcrypto prior to version 1.4.1 exposes sensitive data and allows for the generation of invalid ECDSA signatures. To mitigate this risk, it is crucial to update to the latest version of the package. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for msrcrypto →

Share this vulnerability

FAQ

msrcrypto is an npm package that provides cryptographic functionality for Microsoft Edge. It includes implementations of various cryptographic algorithms, such as ECC.

The vulnerability allows attackers to obtain a server's private ECC key and craft invalid ECDSA signatures, compromising the confidentiality, integrity, and authenticity of cryptographic operations.

No, there is currently no published proof-of-concept for this vulnerability.

To fix this vulnerability, upgrade to version 1.4.1 or later of the msrcrypto package.

No, there are no known workarounds for this vulnerability. Upgrading to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for msrcrypto.

How To Fix

Latest published version: 1.5.8 as of 23 Oct 2026

npm install msrcrypto@1.5.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.4.1

This is the first release that contains the fix.

npm install msrcrypto@1.4.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback