Comodo Internet SecurityApplication · Comodo

CVE-2010-5157

MEDIUM · 6.2 CVSS v2.0 Published 2012-08-25
Fix available
A fix is available. Upgrade to after 4.0.141842.828 or later.
See remediation →
67/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
Race condition in Comodo Internet Security before 4.1.149672.916 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack.

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

A race condition in Comodo Internet Security before version 4.1.149672.916 on Windows XP allows a local attacker to bypass kernel-mode hook handlers by manipulating user-space memory during hook-handler execution. This enables dangerous code execution that would normally be blocked by behavioral detection but not by signature-based malware detection, known as an argument-switch or KHOBE attack.

MitigationUpgrade Comodo Internet Security to version 4.1.149672.916 or later; for systems running Windows XP, consider migrating to a supported operating system as Windows XP is end-of-life.

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
Comodo Internet SecurityApplication
Affected:<= 4.0.141842.828

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

AV:L/AC:H/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. Verify Comodo Internet Security is installed
    Check for Comodo Internet Security in Add/Remove Programs (appwiz.cpl), or look in C:\Program Files\Comodo\ for the installation directory, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Comodo Internet Security
    Affected if Comodo Internet Security is not found on the system, then this CVE does not apply
  2. Identify the installed Comodo Internet Security version
    Open Add/Remove Programs, locate Comodo Internet Security, and note the version number displayed; alternatively, right-click the COMODO icon in the system tray and select About to view the version
    Affected if The displayed version is 4.0.141842.828 or lower, or any version below 4.1.149672.916
  3. Confirm the operating system is Windows XP
    Open command prompt and run 'winver' or check System Properties; the vulnerability specifically affects Windows XP as noted in the CVE description
    Affected if The system is running Windows XP and Comodo Internet Security version is below 4.1.149672.916
  4. Compare installed version against affected range
    If the exact version cannot be determined through the GUI, check the program's version info: right-click the COMODO executable (usually in C:\Program Files\Comodo\Comodo Internet Security\cmd.exe or similar) and select Properties > Details to view the File Version
    Affected if File version shows 4.0.141842.828 or lower, or the version string begins with 4.0 rather than 4.1

A system is affected if Comodo Internet Security is installed with version 4.0.141842.828 or lower on Windows XP, specifically when the behavioral detection hooks are active (they are enabled by default in this product).

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 4.0.141842.828
Interim mitigation

Upgrade Comodo Internet Security to version 4.1.149672.916 or later; for systems running Windows XP, consider migrating to a supported operating system as Windows XP is end-of-life.

Fix this in Comodo Internet Security Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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