CVE-2007-0823: n/a vulnerability

CVE-2007-0823: xterm on Slackware Linux 10.2 stores information that had been displayed for a different user account using...

xterm on Slackware Linux 10.2 stores information that had been displayed for a different user account using the same xterm process, which might allow local users to bypass file permissions and read other users' files, or obtain other sensitive information, by reading the xterm process memory. NOTE: it could be argued that this is an expected consequence of multiple users sharing the same interactive process, in which case this is not a vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 12:34 UTC (UTC+00:00)

Security readout for executives and security teams

This issue concerns possible information leakage when multiple users share the same xterm process on Slackware Linux 10.2. Data previously displayed for one user could remain in process memory and be exposed to another local user. The CVE itself notes this may be expected behavior when users share one interactive process. Exposure appears limited to legacy Slackware Linux 10.2 systems where multiple local users share the same xterm process or interactive terminal context. Remote-only users without local shell or session access are not indicated as exposed by the provided sources. Treat this as a legacy local data exposure risk, not an internet-facing emergency. Priority should be higher only if Slackware 10.2 systems still host sensitive data and allow shared local terminal use. Mitigation focus: Avoid sharing xterm processes across different user accounts.; Terminate terminal sessions before switching users or handing off access.; Restrict local shell access on multi-user legacy systems..

Prepared: Jun 29, 2026, 07:36 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2007-0823 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 7, 2007, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.