Skip to content
Fencer Vulns
high 8.1

CVE-2022-3008 json

Command Injection on tinygltf

published 2022-09-05 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-42444

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

Summary

The tinygltf library uses the C library function wordexp() to perform file path expansion on untrusted paths that are provided from the input file. This function allows for command injection by using backticks. An attacker could craft an untrusted path input that would result in a path expansion. We recommend upgrading to 2.6.0 or past commit 52ff00a38447f06a17eab1caa2cf0730a119c751

Patch / fix

  • syoyo tinygltf 2.6.0
  • tinygltf Debian 14, Debian 13, Debian 12 2.5.0+dfsg-5

debian advisories DEBIAN-CVE-2022-3008

  • tinygltf Ubuntu 22.04 LTS 2.5.0+dfsg-4ubuntu0.1

ubuntu advisories UBUNTU-CVE-2022-3008

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/syoyo/tinygltf/issues/368 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.chromium.org https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49053 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • syoyo tinygltf

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
  • CWE-77 Improper Neutralization of Special Elements used in a Command

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.