CVE-2010-0998
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 · uneditedMultiple stack-based buffer overflows in Free Download Manager (FDM) before 3.0.852 allow remote attackers to execute arbitrary code via vectors involving (1) the folders feature in Site Explorer, (2) the websites feature in Site Explorer, (3) an FTP URI, or (4) a redirect.
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 confidenceFree Download Manager (FDM) versions prior to 3.0.852 contain multiple stack-based buffer overflow vulnerabilities in the Site Explorer component (folders and websites features) and in FTP URI handling/redirect processing. These flaws allow remote attackers to execute arbitrary code by sending specially crafted responses via FTP connections or malicious redirects.
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<= 3.0.851= 2= 2.1= 2.5.700= 2.5.704= 2.5.724= 3.0.843= 3.0.848= 3.0.850CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Free Download Manager installationCheck for FDM installation by looking for 'Free Download Manager' in installed programs on Windows, or checking common installation paths such as C:\Program Files\Free Download Manager or C:\Program Files (x86)\Free Download Manager. On Linux, check /usr/local/fdm or user's home directory for fdm binaries.Affected if Free Download Manager is installed on the system
-
Determine installed FDM versionOpen Free Download Manager and navigate to Help > About, or right-click the executable and select Properties > Details to view the version number. Compare this version against the affected list: 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 prior to 3.0.852.Affected if Installed version is 3.0.851 or lower, or matches any of the specific affected versions listed (2, 2.1, 2.5.700, 2.5.704, 2.5.724, 3.0.843, 3.0.848, 3.0.850)
-
Check Site Explorer component usageLaunch FDM and look for the Site Explorer panel, typically found in the main window under a tab or sidebar labeled 'Site Explorer' or 'Sites'. This component handles folder and website management features.Affected if Site Explorer feature is accessible or has been used to manage folders or websites
-
Verify FTP download functionality usageCheck if any FTP downloads have been added or are active in FDM. Look for ftp:// URIs in the download queue or check download history for entries using FTP protocol.Affected if FTP downloads have been performed or FTP URIs are present in the download list
The system is affected if Free Download Manager version 3.0.851 or lower (or any of the specific versions 2, 2.1, 2.5.700, 2.5.704, 2.5.724, 3.0.843, 3.0.848, 3.0.850) is installed AND the Site Explorer or FTP download features have been used.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade to Free Download Manager version 3.0.852 or later. Since the CVSS score is 10 (Critical) with remote code execution capability, prioritize patching all systems with FDM installed immediately.
Free Download Manager 3.0.852 or later
- 1. Check the currently installed Free Download Manager version (Help > About)
- 2. Download Free Download Manager version 3.0.852 or later from the official vendor website (freedownloadmanager.org)
- 3. Close any running instances of Free Download Manager
- 4. Uninstall the current version of Free Download Manager via Windows Control Panel > Programs and Features
- 5. Run the installer for version 3.0.852 or later
- 6. Follow the installation wizard prompts to complete the installation
- 7. Restart the application and verify the version in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0998 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-0998 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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