CVE-2010-0995
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 · uneditedStack-based buffer overflow in Internet Download Manager (IDM) before 5.19 allows remote attackers to execute arbitrary code via a crafted FTP URI that causes unspecified "test sequences" to be sent from client to server.
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 confidenceStack-based buffer overflow in Internet Download Manager versions before 5.19 allows remote code execution via crafted FTP URIs. When IDM processes specially crafted FTP URIs, it triggers a buffer overflow during client-to-server 'test sequence' communication, enabling arbitrary code execution.
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<= 5.18CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Internet Download Manager installationCheck Program Files for IDMan.exe or look for IDM in the start menu. The typical install path is C:\Program Files\Internet Download Manager\IDMan.exeAffected if IDM is installed on the system
-
Determine installed IDM versionRight-click IDMan.exe, select Properties, then look at the Details tab for version information. Alternatively, open IDM and go to Help > About to view the exact version numberAffected if The version number is 5.18 or lower
-
Verify if FTP download functionality is activeIDM must be configured to handle FTP protocol downloads. Check IDM's Options > General settings to see if FTP is enabled under the protocol handlersAffected if FTP protocol handler is enabled and IDM is set as the default handler for ftp:// URLs
-
Confirm IDM is processing FTP URIsAttempt to initiate an FTP download through IDM or check if the application automatically intercepts ftp:// links in browsers. IDM must be actively processing FTP URIs for the vulnerable code path to executeAffected if IDM is processing or intercepting FTP download requests
You are affected if Internet Download Manager version 5.18 or lower is installed and FTP download functionality is enabled or accessible on the system.
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 Internet Download Manager to version 5.19 or later to remediate this vulnerability.
Internet Download Manager 5.19 or later
- Download Internet Download Manager version 5.19 or later from the official website (www.internetdownloadmanager.com)
- Install the updated version following the installation wizard prompts
- Verify the installation by checking Help > About in IDM to confirm version 5.19 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0995 — 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-0995 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