CVE-2022-36313
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 · uneditedAn issue was discovered in the file-type package before 16.5.4 and 17.x before 17.1.3 for Node.js. A malformed MKV file could cause the file type detector to get caught in an infinite loop. This would make the application become unresponsive and could be used to cause a DoS attack.
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 confidenceThe file-type npm package for Node.js has a denial-of-service vulnerability where a malformed MKV (Matroska video) file causes the file type detector to enter an infinite loop, making the application unresponsive. This is triggered during file type detection when processing specifically crafted MKV input.
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< 16.5.4>= 17.0.0, < 17.1.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the installed file-type package versionRun 'npm list file-type' or check the package.json dependencies to see the exact version of the file-type package installed in your projectAffected if The version is less than 16.5.4, or is 17.0.0 through 17.1.2 (inclusive)
-
Determine if your application processes MKV filesSearch your codebase for .mkv file handling, look for file-type being called on files with .mkv extension, or inspect network/file upload handlers that may pass MKV files to file-type for detectionAffected if Your application uses file-type to detect or validate Matroska (.mkv) video files
-
Check for runtime version in node_modulesInspect the file-type package version directly: look at node_modules/file-type/package.json or run 'npm view file-type version' to confirm what version is installedAffected if The resolved version matches the vulnerable ranges listed above
You are affected if you have file-type version below 16.5.4 or between 17.0.0 and 17.1.2 AND your application uses file-type to process MKV files, as this combination triggers the infinite loop vulnerability.
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 · scoped16.5.417.1.3
Update the file-type package to version 16.5.4 or later (16.x) or 17.1.3 or later (17.x). If immediate patching is not possible, implement timeout mechanisms around file-type detection operations and restrict file-type detection to trusted, validated input sources.
[email protected] or [email protected]
- Identify the file-type package in your project (check package.json dependencies)
- Run 'npm list file-type' to see the current installed version
- Run 'npm install [email protected]' or 'npm install [email protected]' to upgrade to a fixed version
- Run 'npm audit' to verify the fix was applied
- Rebuild and redeploy your application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing4.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,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36313 — 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-36313 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