CVE-2022-25927 is a Regular Expression Denial of Service vulnerability in ua-parser-js. Affected versions include releases from 0.7.30 and earlier before 0.7.33, and from 0.8.1 before 1.0.33. The flaw is triggered via the library's trim() function, where crafted excessively long user-agent input can cause catastrophic backtracking or otherwise excessive regular-expression processing. The issue can be reached when applications pass untrusted user-agent strings or similar attacker-controlled input into ua-parser-js for parsing, allowing the vulnerable regex handling to consume disproportionate CPU resources.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a minimal Node.js proof-of-concept for CVE-2022-25927 affecting ua-parser-js 0.7.31. It contains only two files: package.json and test_parser.js. The package manifest defines a simple test environment and pins the vulnerable dependency. The JavaScript file creates an HTTP server using Node's built-in http module, reads the incoming User-Agent header, passes it into UAParser via setUA(), and then calls getResult(). The comment in code explicitly identifies this call as the point where the ReDoS condition is triggered and the server hangs. The exploit capability is denial of service, not code execution: an attacker sends a specially crafted HTTP request with a malicious User-Agent string to the listening server, causing excessive regex processing and blocking the Node.js event loop. There are no outbound network callbacks, shells, persistence mechanisms, or secondary payloads. The repository is structured purely as a local reproducible test harness to demonstrate the vulnerability in a server-side usage pattern of ua-parser-js.
This repository is a proof-of-concept exploit for CVE-2022-25927, a vulnerability in the ua-parser-js library. The main exploit logic is in 'main.js', which sets up an HTTP server on port 3000. For each incoming request, it constructs an extremely large user-agent string (over 200,000 characters) and parses it using ua-parser-js. This is intended to trigger excessive resource consumption or a denial-of-service condition in vulnerable versions of ua-parser-js. The repository includes the vulnerable library as a dependency under 'node_modules/'. The exploit demonstrates the issue but does not provide a weaponized or automated attack; it is a POC for research and demonstration purposes. No hardcoded remote endpoints are present, but the exploit is network-accessible via the local HTTP server on port 3000.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Denial-of-service vulnerability in the ua-parser-js dependency affecting Bitbucket Data Center.
Denial-of-service vulnerability in ua-parser.js allowing an unauthenticated attacker to cause service unavailability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.