CVE-2018-10922 json
An input validation flaw exists in ttembed.
published 2018-08-02 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-2976
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
An input validation flaw exists in ttembed. With a crafted input file, an attacker may be able to trigger a denial of service condition due to ttembed trusting attacker controlled values.
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-2018-10922 updated cvss 7.5
ttembed: use of untrusted length field may lead to denial of service
-
Red Hat Enterprise Linux 7 ttembedaffected: no fix planned “Will not fix”
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
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10922 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/hisdeedsaredust/ttembed/issues/2 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- [UNKNOWN] ttembed
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2018-10922
exploit, issue-tracking, third-party-advisory
-
github.com
/hisdeedsaredust/ttembed/issues/2
exploit, third-party-advisory
Sources
- CVE List CVE-2018-10922
- NVD CVE-2018-10922
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.