dbcve.org
No Ip2Application · No Ip

CVE-2008-5369

MEDIUM · 6.9 CVSS v2.0 Published 2008-12-08
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
noip2 in noip2 2.1.7 allows local users to overwrite arbitrary files via a symlink attack on the /tmp/noip2 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 noip2 client version 2.1.7 creates a temporary file at /tmp/noip2 without checking for existing symlinks, allowing a local attacker to pre-create a symlink at that path and cause the application to overwrite arbitrary files with attacker-controlled content.

MitigationReplace the insecure temporary file creation with secure methods such as mkstemp() or O_EXCL flag, which atomically create files and fail if a symlink already exists.

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
No Ip2Application
Affected:= 2.1.7

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 noip2 client is installed
    Run 'which noip2' or look for the binary in common locations like /usr/local/bin/noip2, /usr/bin/noip2, or /usr/sbin/noip2
    Affected if noip2 binary is not found on the system
  2. Identify the installed noip2 version
    Run 'noip2 -V' or 'noip2 -v' to display version information
    Affected if The version displayed is exactly 2.1.7
  3. Check for existing /tmp/noip2 file or symlink
    Run 'ls -la /tmp/noip2' to inspect if a file or symlink already exists at that path
    Affected if A symlink at /tmp/noip2 exists pointing to a location you did not create
  4. Verify the process runs with elevated privileges
    Check if noip2 is configured to run as root or with setuid bit using 'ls -la $(which noip2)' and review any systemd service or init script
    Affected if noip2 runs with root privileges and could overwrite files owned by root via the symlink attack

You are affected only if noip2 version 2.1.7 is installed and the /tmp/noip2 symlink can be pre-created by a local attacker to trigger 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 the insecure temporary file creation with secure methods such as mkstemp() or O_EXCL flag, which atomically create files and fail if a symlink already exists.

Fix this in No Ip2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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