Skip to content
Fencer Vulns
medium 5.5

CVE-2022-36313 json

file-type vulnerable to Infinite Loop via malformed MKV file

published 2022-07-21 4 y ago modified 2026-10-07 32 d ago also GHSA-mhxj-85r3-2x55 , EUVD-2022-6377

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

An 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.

Patch / fix

  • npm file-type 16.5.4, 17.1.3
  • sindresorhus file-type 16.5.4, 17.1.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-36313 updated cvss 5.5

file-type: a malformed MKV file could cause the file type detector to get caught in an infinite loop

  • Red Hat Migration Toolkit for Virtualization migration-toolkit-virtualization/mtv-ui-rhel8 Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-docs-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator
    affected: no fix available
  • Red Hat Integration Camel K 1 file-type
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Dev Spaces devspaces/code-rhel8, devspaces-theia-rhel8-container, devspaces-theia-endpoint-rhel8-container
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat Data Grid 8.4.1
    fixed: vendor fix RHSA-2023:0713
  • Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-central-db-rhel8 Red Hat build of Apicurio Registry 2 file-type Red Hat OpenShift Dev Spaces devspaces/idea-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
32 d ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm file-type
>=13.0.0, <16.5.4
>=17.0.0, <17.1.3
16.5.4
17.1.3

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.