LiveActive security incident?Get immediate response
CVE Record

CVE-2010-2023: transports/appendfile.c in Exim before 4.72, when a world-writable sticky-bit mail directory is used, does...

transports/appendfile.c in Exim before 4.72, when a world-writable sticky-bit mail directory is used, does not verify the st_nlink field of mailbox files, which allows local users to cause a denial of service or possibly gain privileges by creating a hard link to another user's file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Exim issue affects local mail delivery when a world-writable sticky-bit mail directory is used. A local user could abuse hard links so Exim mishandles another user’s mailbox file, causing denial of service or possibly privilege escalation. It is mainly a risk on shared Unix-like systems running Exim before 4.72. Exposure is most likely on legacy systems running Exim before 4.72 with local users and world-writable sticky-bit mail directories used for mailbox delivery. Modern vendor-maintained packages are less likely to remain exposed, but old appliances, shared hosting, and unmanaged mail servers should be checked. Prioritize remediation for shared systems, hosting platforms, and servers with local users. For single-purpose mail gateways without local users and with current vendor packages, urgency is lower. Because the issue can cross local user boundaries, legacy Exim estates should still be cleaned up deliberately. Mitigation focus: Upgrade Exim to 4.72 or a vendor-supported fixed package.; Review vendor advisories from your distribution for backported fixes.; Avoid vulnerable world-writable sticky-bit mailbox directory configurations where possible..

Prepared

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-2010-2023 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
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
3Source links

CVSS and timeline data

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

Source materials

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.