dbcve.org
VdrApplication

CVE-2005-0071

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
vdr before 1.2.6 does not securely create files, which allows attackers to overwrite arbitrary files.

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 · moderate confidence

vdr (Video Disk Recorder) before version 1.2.6 insecurely creates files, allowing local attackers to overwrite arbitrary files on the system, likely through a symlink attack or TOCTOU (time-of-check-time-of-use) race condition in temporary file creation.

MitigationUpgrade vdr to version 1.2.6 or later to obtain the security fix. If upgrading is not immediately possible, review and restrict file creation permissions in the vdr process environment.

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
VdrApplication
Affected:= 1.0.0= 1.0.4= 1.2.0= 1.2.1= 1.2.2= 1.2.5

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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/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. Determine installed VDR version
    Run 'vdr --version' or check package manager: 'dpkg -l vdr' (Debian) or 'rpm -q vdr' (RHEL)
    Affected if Version is 1.0.0, 1.0.4, 1.2.0, 1.2.1, 1.2.2, or 1.2.5
  2. Check if VDR service is running
    Run 'ps aux | grep vdr' or 'systemctl status vdr'
    Affected if VDR is actively running and creating temporary files
  3. Locate VDR temporary files
    Check common temp directories: 'ls -la /tmp/*vdr*' and 'ls -la /var/tmp/*vdr*'
    Affected if Temporary files or directories created by VDR exist with permissive permissions
  4. Verify temp file permissions
    Run 'ls -la' on VDR's temporary files and check for world-writable permissions or lack of file ownership checks
    Affected if Temporary files are world-writable or created without secure file handling

You are affected if VDR version is 1.0.0, 1.0.4, 1.2.0, 1.2.1, 1.2.2, or 1.2.5 and the service is actively running with insecure temporary file creation in shared directories.

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

Upgrade vdr to version 1.2.6 or later to obtain the security fix. If upgrading is not immediately possible, review and restrict file creation permissions in the vdr process environment.

Fix this in Vdr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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