CVE-2023-40359
First published: Mon Aug 14 2023(Updated: )
xterm before 380 supports ReGIS reporting for character-set names even if they have unexpected characters (i.e., neither alphanumeric nor underscore), aka a pointer/overflow issue. This can only occur for xterm installations that are configured at compile time to use a certain experimental feature.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| xterm | <380 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-40359?
CVE-2023-40359 is classified as a moderate severity vulnerability.
How do I fix CVE-2023-40359?
To fix CVE-2023-40359, update xterm to version 380 or later.
What issues are caused by CVE-2023-40359?
CVE-2023-40359 can lead to a pointer/overflow issue due to unexpected characters in ReGIS reporting.
Which versions of xterm are affected by CVE-2023-40359?
CVE-2023-40359 affects all xterm versions below 380.
What feature triggers the vulnerability in CVE-2023-40359?
The vulnerability in CVE-2023-40359 is triggered when xterm is configured at compile time to use a specific experimental feature.
- agent/type
- agent/softwarecombine
- agent/severity
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- agent/author
- vendor/invisible-island
- canonical/xterm