dbcve.org
Internet SecurityApplication · Comodo

CVE-2024-7251

HIGH · 7.8 CVSS v3.1 Published 2024-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Comodo Internet Security Pro cmdagent Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Comodo Internet Security Pro. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the cmdagent executable. By creating a symbolic link, an attacker can abuse the agent to create a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-22832.

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

This is a local privilege escalation vulnerability in Comodo Internet Security Pro's cmdagent executable. The flaw allows an attacker with low-privileged code execution to create a symbolic link and abuse cmdagent's file creation functionality to place files in arbitrary locations with SYSTEM privileges, leading to full privilege escalation.

MitigationApply vendor-supplied patches for Comodo Internet Security Pro when available. In the interim, restrict write access to directories where cmdagent operates and monitor for suspicious symbolic link creation.

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

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 installation by looking in Program Files for Comodo folder, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Comodo*"}'
    Affected if No Comodo product is found, then not affected by this specific CVE
  2. Check installed version matches affected release
    Run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Comodo*"}' or check Program Files\Comodo\Common\version.ini for version number
    Affected if Version equals 12.2.4.8032 exactly - this is the only affected version listed
  3. Locate cmdagent executable
    Search for cmdagent.exe in Comodo installation directories - typically in Program Files\Comodo\COMODO Internet Security\ or Program Files\Comodo\Common\, use 'Get-ChildItem -Path "C:\Program Files\Comodo" -Recurse -Filter "cmdagent.exe" -ErrorAction SilentlyContinue'
    Affected if cmdagent.exe exists in the Comodo installation directory - this is the vulnerable component
  4. Verify cmdagent service is running with SYSTEM privileges
    Run 'Get-Service -Name *Comodo*' and check 'sc queryex cmdagent' to see if the service runs under the SYSTEM account
    Affected if cmdagent service runs under Local System or SYSTEM account - this is required for the privilege escalation to yield SYSTEM access
  5. Check permissions on Comodo directories
    Review ACLs on directories where cmdagent writes files using 'Get-Acl "C:\Program Files\Comodo\*" | Select-Object Path, AccessToString' - look for weak permissions allowing low-privileged users to write
    Affected if Non-admin users have write access to Comodo directories where cmdagent operates - this enables the symbolic link attack vector

Environment is affected only if Comodo Internet Security version 12.2.4.8032 is installed, cmdagent.exe is present and runs as SYSTEM, and low-privileged users have write access to directories cmdagent uses for file creation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for Comodo Internet Security Pro when available. In the interim, restrict write access to directories where cmdagent operates and monitor for suspicious symbolic link creation.

Fix this in Internet Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-7251 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