CVE-2022-36034
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 · uneditednitrado.js is a type safe wrapper for the Nitrado API. Possible ReDoS with lib input of `{{` and with many repetitions of `{{|`. This issue has been patched in all versions above `0.2.5`. There are currently no known workarounds.
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 confidencenitrado.js versions 0.2.5 and below contain a ReDoS (Regular Expression Denial of Service) vulnerability. The vulnerability is triggered by user-supplied input containing the pattern `{{` or repeated sequences of `{{|`, which causes the regex engine to consume excessive CPU resources, potentially crashing the service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.2.5CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify nitrado.js installationRun 'npm list nitrado.js' in your project directory or check package.json dependencies for nitrado.jsAffected if nitrado.js is listed as a dependency in your project
-
Determine installed versionRun 'npm list nitrado.js' or check the installed version in node_modules/nitrado.js/package.jsonAffected if The installed version is 0.2.5 or below, or the version field shows a number less than 0.2.5
-
Identify code paths processing user inputSearch your codebase for usages of nitrado.js functions that accept user input, particularly any that process template-like patternsAffected if Your code passes user-supplied input to nitrado.js functions without sanitization
-
Inspect regex patterns in nitrado.jsExamine the nitrado.js source code in node_modules/nitrado.js for regex patterns involving '{{' or '{{|'Affected if The library contains regex patterns that match on '{{' or '{{|' sequences and these patterns are used when processing external input
Your environment is affected if nitrado.js version 0.2.5 or below is installed AND user-supplied input can reach the vulnerable regex patterns in the library.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.2.5
Upgrade nitrado.js to any version above 0.2.5. There are no known workarounds for this vulnerability.
0.2.5 or higher
- Update the nitrado.js dependency in package.json to version 0.2.5 or higher
- Run 'npm install' or 'yarn install' to update the package
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36034 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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