CVE-2022-24300 json
Minetest before 5.4.0 allows attackers to add or modify arbitrary meta fields of the same item stack as saved user input, aka ItemStack met…
published 4y ago modified 4mo ago also EUVD-2022-29201
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Minetest before 5.4.0 allows attackers to add or modify arbitrary meta fields of the same item stack as saved user input, aka ItemStack meta injection.
Patch / fix
Is CVE-2022-24300 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-24300 updated cvss 8.2
minetest-server: ItemStack meta injection vulnerability in Minetest
-
Red Hat All currently supported Red Hat productsnot 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
Exploit prediction
1.67% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
github.com
/minetest/minetest/commit/b5956bde259faa240a81060ff4e598e25ad52dae
patch, third-party-advisory
-
bugs.debian.org
/1004223
mailing-list, patch, third-party-advisory
-
github.com
/minetest/minetest/security/advisories/GHSA-hwj2-xf72-r4cf
patch, third-party-advisory
-
debian.org
/security/2022/dsa-5075
vendor-advisory, mailing-list, third-party-advisory
Sources
- CVE List CVE-2022-24300
- NVD CVE-2022-24300
Fencer Intel 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.