LiveActive security incident?Get immediate response
CVE Record

CVE-2004-0564: Roaring Penguin pppoe (rp-ppoe), if installed or configured to run setuid root contrary to its design, allo...

Roaring Penguin pppoe (rp-ppoe), if installed or configured to run setuid root contrary to its design, allows local users to overwrite arbitrary files. NOTE: the developer has publicly disputed the claim that this is a vulnerability because pppoe "is NOT designed to run setuid-root." Therefore this identifier applies *only* to those configurations and installations under which pppoe is run setuid root despite the developer's warnings.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2004-0564 concerns rp-pppoe only when the pppoe program is installed or configured to run setuid root, which the developer said is outside its design. In that unsafe configuration, a local user may overwrite arbitrary files, creating potential integrity and privilege-escalation risk. Exposure is most likely on legacy Linux or Unix systems with rp-pppoe installed and the pppoe binary granted setuid-root privileges. Standard installations that do not run pppoe setuid root may be outside the CVE scope, based on the CVE note. Treat this as a targeted legacy-configuration cleanup, not an internet-wide emergency. Prioritize systems with local multi-user access or sensitive files, especially old Linux distributions still using rp-pppoe. Mitigation focus: Remove setuid-root privileges from pppoe unless vendor guidance explicitly requires them.; Apply relevant rp-pppoe updates from the operating-system vendor for affected legacy systems.; Review vendor advisories before changing production PPPoE authentication or network startup behavior..

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-2004-0564 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
2Source 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.