dbcve.org
RccpApplication · Zak B Elep

CVE-2008-4980

MEDIUM · 6.9 CVSS v2.0 Published 2008-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
delqueueask in rccp 0.9 allows local users to overwrite arbitrary files via a symlink attack on the /tmp/cccp_tmp.txt temporary file.

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 delqueueask function in rccp 0.9 creates and writes to a temporary file at /tmp/cccp_tmp.txt without proper validation. A local attacker can exploit this by pre-creating a symbolic link at that path, causing the application to overwrite an arbitrary target file when the vulnerable code executes.

MitigationReplace direct file operations with secure temporary file creation methods such as mkstemp() or use a uniquely named temp file with appropriate permissions in a non-predictable location.

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
RccpApplication
Affected:= 0.9

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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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. Check if rccp is installed
    Run 'which rccp' or 'rpm -qa | grep rccp' (RHEL) or 'dpkg -l | grep rccp' (Debian) to locate the rccp binary
    Affected if rccp is not found on the system, then the vulnerability does not apply
  2. Determine the installed version of rccp
    Run 'rccp --version' or 'rccp -v' to output the version number
    Affected if The version is 0.9, indicating the affected version
  3. Inspect the delqueueask function behavior
    Run 'strings <path_to_rccp_binary> | grep cccp_tmp' or use 'nm rccp' to examine if the binary references the /tmp/cccp_tmp.txt path
    Affected if The binary contains references to /tmp/cccp_tmp.txt and the delqueueask function is present, confirming the vulnerable code path exists
  4. Verify symlink attack feasibility
    Check if /tmp/cccp_tmp.txt already exists as a symlink by running 'ls -la /tmp/ccccp_tmp.txt'
    Affected if A symlink already exists at /tmp/cccp_tmp.txt, indicating active exploitation or prior attack attempt

A system is affected if rccp version 0.9 is installed and the application has permissions to write to /tmp, allowing a local attacker to pre-create a symlink at /tmp/cccp_tmp.txt for arbitrary file overwrite.

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

Replace direct file operations with secure temporary file creation methods such as mkstemp() or use a uniquely named temp file with appropriate permissions in a non-predictable location.

Fix this in Rccp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-4980 — 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-2008-4980 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