Free Download ManagerApplication · Freedownloadmanager

CVE-2010-0999

HIGH · 7.1 CVSS v2.0 Published 2010-05-17
Fix available
A fix is available. Upgrade to after 3.0.851 or later.
See remediation →
80/100
Remediation priority · High
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
Directory traversal vulnerability in Free Download Manager (FDM) before 3.0.852 allows remote attackers to create arbitrary files via directory traversal sequences in the name attribute of a file element in a metalink 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

Directory traversal vulnerability in Free Download Manager before version 3.0.852 allows remote attackers to create arbitrary files on the target system by embedding directory traversal sequences (e.g., ../../) in the name attribute of file elements within metalink files. The application fails to properly sanitize file paths in metalink file parsing.

MitigationUpgrade Free Download Manager to version 3.0.852 or later, which contains the patch for the directory traversal vulnerability in metalink file processing. Alternatively, avoid processing untrusted metalink files from unknown sources.

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
Free Download ManagerApplication
Affected:<= 3.0.851= 2= 2.1= 2.5.700= 2.5.704= 2.5.724= 3.0.843= 3.0.848= 3.0.850

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

AV:N/AC:M/Au:N/C:N/I:C/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. Identify installed Free Download Manager version
    Open Free Download Manager and navigate to Help > About, or check the program's version information in your system's installed programs list. Compare the version number against the affected ranges: versions 2, 2.1, 2.5.700, 2.5.704, 2.5.724, 3.0.843, 3.0.848, 3.0.850, or any version 3.0.851 or earlier.
    Affected if The installed version is 3.0.851 or lower, or matches any of the specific affected versions listed (2.x, 2.1, 2.5.7xx, 3.0.843, 3.0.848, 3.0.850)
  2. Determine if metalink file processing is used
    Review your download history or examine any .metalink files you have downloaded or processed with Free Download Manager. Check if the application has a metalink handler or parser feature enabled in its settings.
    Affected if You have processed or regularly process metalink files with the application
  3. Inspect recent download activity for metalink files
    Access the application's download manager or log files to see if metalink files (.metalink extension) have been added as downloads. Look for entries in the download queue that reference metalink format.
    Affected if Metalink files appear in your download history or queue
  4. Verify metalink parsing behavior
    If you have a test metalink file available, observe whether the application extracts files to locations outside the intended download directory when the metalink contains path elements with directory traversal sequences (../../).
    Affected if The application processes metalink files and allows path traversal outside the intended directory

You are affected if you are running any Free Download Manager version from 2.0 through 3.0.851 and have processed or intend to process metalink files with the application.

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
Upgrade available Upgrade to a release after 3.0.851
Interim mitigation

Upgrade Free Download Manager to version 3.0.852 or later, which contains the patch for the directory traversal vulnerability in metalink file processing. Alternatively, avoid processing untrusted metalink files from unknown sources.

Fix this in Free Download Manager 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 the upgrade done

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-2010-0999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2010-0999 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