CVE-2010-5185
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 · uneditedThe Antivirus component in Comodo Internet Security before 5.3.174622.1216 does not check whether X.509 certificates in signed executable files have been revoked, which has unknown impact and remote attack vectors.
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 confidenceThe Comodo Internet Security antivirus component before version 5.3.174622.1216 fails to perform certificate revocation checks on X.509 certificates embedded in signed executable files. This allows potentially malicious code signed with revoked or compromised certificates to bypass the antivirus security validation, as the system does not verify whether the signing certificate has been revoked via CRL or OCSP.
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.0.163652.1142= 3.0.14.276= 3.0.15.277= 3.0.16.295= 3.0.17.304= 3.0.18.309= 3.0.19.318= 3.0.20.320= 3.0.22.349= 3.0.23.364= 3.0.24.368= 3.0.25.378CVSS 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.
-
Confirm Comodo Internet Security is installedLook for Comodo Internet Security in the list of installed programs via Control Panel > Programs and Features, or check for Comodo antivirus processes running in Task Manager.Affected if Comodo Internet Security is present on the system
-
Locate the installed version numberOpen Comodo Internet Security, navigate to Help > About, or right-click the COMODO icon in the system tray and select About. The version is typically displayed in the format X.X.XXXXXX.XXXX.Affected if Unable to retrieve version information from the Comodo installation
-
Compare the version against the affected rangesCompare your installed version number to the following affected versions: any version <= 5.0.163652.1142, or specifically versions 3.0.14.276, 3.0.15.277, 3.0.16.295, 3.0.17.304, 3.0.18.309, 3.0.19.318, 3.0.20.320, 3.0.22.349, 3.0.23.364, 3.0.24.368, or 3.0.25.378.Affected if Your installed version matches or falls within these affected version ranges
If Comodo Internet Security is installed and the version is either <= 5.0.163652.1142 or matches one of the listed 3.0.x versions, the certificate revocation checking vulnerability is present in your environment.
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 Comodo Internet Security to version 5.3.174622.1216 or later, which implements proper X.509 certificate revocation checking for signed executables. Until upgraded, exercise extreme caution with any signed executable, even from seemingly trusted sources.
Comodo Internet Security 5.3.174622.1216 or later
- 1. Check current Comodo Internet Security version by opening the application and navigating to Help > About
- 2. Navigate to the official Comodo download page at comodo.com to obtain version 5.3.174622.1216 or later
- 3. Download the installer for Comodo Internet Security 5.3.174622.1216
- 4. Close any running Comodo components and disable real-time protection temporarily
- 5. Run the installer and follow the on-screen prompts to complete the upgrade
- 6. Restart the computer when prompted
- 7. After restart, verify the new version by checking Help > About to confirm version 5.3.174622.1216 or higher is installed
- 8. Re-enable any protection features that were temporarily disabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5185 — 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-5185 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