Lucene search
K

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.

🗓️ 23 Aug 2023 07:00:00Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 5 Views

Xterm before 380 allows ReGIS reporting of character-set names with unexpected characters, risking pointer overflow when compiled with an experimental feature.

Related
Detection
Vulners

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

23 Aug 2023 07:00Current
7.2High risk
Vulners AI Score7.2
CVSS 3.19.8
EPSS0.00734
SSVC
5