cve.bz

CVE-2018-3738 protobufjs project protobufjs: Incorrect Regular Expression

5.5 mediumExploit referenceEPSS 0.9%Fix available

Medium (5.5) in protobufjs project protobufjs. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in protobufjs 5.0.3, 6.8.6.

protobufjs is vulnerable to ReDoS when parsing crafted invalid .proto files.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 62nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-185 Incorrect Regular Expression
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-3738 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-3738?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-3738?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-3738 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
protobufjs_project:protobufjsthrough 6.8.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-762f-c2wg-m8c8npmprotobufjs>=6.0.0 <6.8.66.8.6
GHSA-762f-c2wg-m8c8npmprotobufjs<5.0.35.0.3

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON