dbcve.org
Advanced Malware Protection For EndpointsApplication · Cisco

CVE-2018-0237

MEDIUM · 5.8 CVSS v3.1 Published 2018-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability in the file type detection mechanism of the Cisco Advanced Malware Protection (AMP) for Endpoints macOS Connector could allow an unauthenticated, remote attacker to bypass malware detection. The vulnerability occurs because the software relies on only the file extension for detecting DMG files. An attacker could exploit this vulnerability by sending a DMG file with a nonstandard extension to a device that is running an affected AMP for Endpoints macOS Connector. An exploit could allow the attacker to bypass configured malware detection. Cisco Bug IDs: CSCve34034.

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

The AMP for Endpoints macOS Connector uses file extension only to identify DMG (Apple Disk Image) files for malware scanning. Attackers can bypass detection by renaming DMG files with non-standard extensions (e.g., .dmg.txt or .dmg.exe), causing the scanner to treat the file as non-DMG content and skip DMG-specific analysis.

MitigationApply the vendor patch from Cisco when available. Until then, consider disabling or restricting DMG file downloads, or implement additional file content-based detection at network perimeter.

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
Advanced Malware Protection For EndpointsApplication
Affected:= 1.4\(5\)

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

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

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. Check installed AMP for Endpoints version
    On macOS endpoints, locate the installed Cisco AMP for Endpoints connector version. This is typically found in the application properties, About screen, or via command line tools provided by the AMP agent. Compare the exact version number to the affected version 1.4(5).
    Affected if The installed version matches 1.4(5)
  2. Verify DMG scanning is enabled
    Examine the AMP for Endpoints scanning policy or configuration on the macOS connector. Look for settings that control whether DMG files are scanned. This may be in the GUI policy settings, a configuration file, or the agent preferences.
    Affected if DMG file scanning is enabled in the AMP configuration
  3. Identify how DMG files are identified for scanning
    Review the AMP connector configuration to determine if file type identification relies solely on file extension matching. Look for rules or patterns that specify extensions (such as .dmg) for triggering DMG-specific analysis versus content-based detection.
    Affected if The connector identifies DMG files by extension only without content-type validation
  4. Test with renamed DMG file
    Create a test DMG file and rename it with a non-standard extension (such as .dmg.txt or .dmg.exe). Submit or scan this file through the AMP connector and observe whether it receives DMG-specific analysis or is treated as a different file type.
    Affected if The renamed file receives different/lesser scanning than a properly named .dmg file

A system is affected if it runs AMP for Endpoints version 1.4(5) with DMG file scanning enabled using extension-only identification, where renamed DMG files bypass DMG-specific analysis.

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 the vendor patch from Cisco when available. Until then, consider disabling or restricting DMG file downloads, or implement additional file content-based detection at network perimeter.

Fix this in Advanced Malware Protection For Endpoints Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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