Out-of-bounds write in AT&T
Priority LOW 34CWE-787Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
Within the function HandleFileArg the argument filepattern is under control of the user who passes it in from the command line. filepattern is passed directly to memcpy copying the path provided by the user into a staticly sized buffer without any length checks resulting in a stack-buffer overflow.
Why it matters now
EPSS 0.00333 26th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | AT&T | AT&T Labs Xmill 0.7 | — | No fix listed | CNA |
- AT&T Vendor— Affected AT&T Labs Xmill 0.7 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2021-21813
- 2026-10-03 Alias added: GHSA-h458-372j-6g45
References
More AT&T Xmill vulnerabilities
- TI-2022-09848 A heap-based buffer overflow exists in XML Decompression DecodeTreeBlock in AT&T Labs… CVSS 3.1CRITICAL 9.8
- TI-2021-04874 Heap-based buffer overflow in AT&T CVSS 3.1CRITICAL 9.8
- TI-2021-04875 Heap-based buffer overflow in AT&T CVSS 3.1CRITICAL 9.8
- TI-2021-04870 Heap-based buffer overflow in AT&T CVSS 3.1CRITICAL 9.8
- TI-2021-04873 Buffer overflow in AT&T CVSS 3.1CRITICAL 9.8
- TI-2021-04872 Buffer overflow in AT&T CVSS 3.1CRITICAL 9.8
Sources
- CVE-2021-21813 · CVE Program
- CVE-2021-21813 · NVD
- FIRST EPSS
- GHSA-h458-372j-6g45 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences