dbcve.org
Suse LinuxOperating system · Suse

CVE-2006-2752

MEDIUM · 6.4 CVSS v2.0 Published 2006-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The RedCarpet /etc/ximian/rcd.conf configuration file in Novell Linux Desktop 9 and SUSE SLES 9 has world-readable permissions, which allows attackers to obtain the rc (RedCarpet) password.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RedCarpet configuration file /etc/ximian/rcd.conf on Novell Linux Desktop 9 and SUSE SLES 9 is stored with world-readable permissions (likely 644), allowing any local user to read the file and obtain the rc (RedCarpet) service password stored in plain text.

MitigationChange file permissions on /etc/ximian/rcd.conf to restrict read access (chmod 600 or 640) and change the compromised RedCarpet password since it may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Suse LinuxOperating system
Affected:= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the configuration file exists
    Check if /etc/ximian/rcd.conf is present on the system using: ls -la /etc/ximian/rcd.conf
    Affected if The file exists on the system (Novell Linux Desktop 9 or SUSE SLES 9)
  2. Check file permissions
    Run: stat -c '%a' /etc/ximian/rcd.conf or ls -la /etc/ximian/rcd.conf to view the permission bits
    Affected if Permissions are 644 or any setting that grants read access to 'others' (e.g., 644, 646, 654, 666)
  3. Verify world-readable status
    Run: test -r /etc/ximian/rcd.conf && test -O /etc/ximian/rcd.conf || echo 'world-readable' to confirm any user can read the file
    Affected if The file is readable by non-privileged users (world-readable or group-readable with vulnerable group ownership)
  4. Confirm plain text password presence
    Inspect the file contents with: cat /etc/ximian/rcd.conf or grep -i 'password' /etc/ximian/rcd.conf
    Affected if The file contains an unencrypted password string (rc service password in plain text)

The system is affected if /etc/ximian/rcd.conf exists and is readable by any local user, exposing the RedCarpet service password in plain text.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change file permissions on /etc/ximian/rcd.conf to restrict read access (chmod 600 or 640) and change the compromised RedCarpet password since it may have been exposed.

Fix this in Suse Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-2752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-2752 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data