dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2024-20361

MEDIUM · 5.8 CVSS v3.1 Published 2024-05-22
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 Object Groups for Access Control Lists (ACLs) feature of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to bypass configured access controls on managed devices that are running Cisco Firepower Threat Defense (FTD) Software. This vulnerability is due to the incorrect deployment of the Object Groups for ACLs feature from Cisco FMC Software to managed FTD devices in high-availability setups. After an affected device is rebooted following Object Groups for ACLs deployment, an attacker can exploit this vulnerability by sending traffic through the affected device. A successful exploit could allow the attacker to bypass configured access controls and successfully send traffic to devices that are expected to be protected by the affected device.

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 vulnerability in Cisco FMC's Object Groups for ACLs feature causes incorrect deployment to managed FTD devices in high-availability setups. After a reboot following Object Groups for ACLs deployment, the ACLs fail to apply correctly, allowing unauthenticated remote attackers to bypass configured access controls and reach protected internal networks.

MitigationApply Cisco-provided patches for FMC when available. In the interim, avoid using Object Groups for ACLs in high-availability FTD deployments or manually verify ACL deployment and functionality after any reboot of affected devices.

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
Secure Firewall Management CenterApplication
Affected:= 7.1.0= 7.1.0.1= 7.1.0.2= 7.1.0.3= 7.2.0= 7.2.0.1= 7.2.1= 7.2.2= 7.2.3= 7.2.3.1= 7.3.0= 7.3.1

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. Verify FMC version
    Access the Cisco FMC web interface and navigate to the System > About page, or use the CLI and run 'show version' to determine the installed FMC version.
    Affected if The installed version matches any of these: 7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.2.0, 7.2.0.1, 7.2.1, 7.2.2, 7.2.3, 7.2.3.1, 7.3.0, or 7.3.1
  2. Confirm Object Groups for ACLs feature is in use
    In the FMC web interface, navigate to the ACL policy configuration and inspect whether any Access Control Lists contain object groups (network objects, service objects, or object groups) rather than only individual host/IP entries.
    Affected if Object Groups are configured and deployed as part of Access Control Lists on the FMC
  3. Confirm high-availability FTD deployment
    In the FMC web interface, navigate to Devices > Device Management and check if any Firepower Threat Defense (FTD) devices are configured in high-availability pairs.
    Affected if There are FTD devices running in high-availability mode managed by this FMC
  4. Check ACL functionality after reboot
    Following any reboot of the managed FTD devices, verify that the deployed ACL rules are actually being applied by reviewing the FTD connection tables, traffic logs, or by attempting to source traffic that should be permitted or denied by the configured ACLs.
    Affected if After a reboot, traffic is being allowed or denied inconsistently with the configured ACL policies, indicating the rules are not applying correctly

You are affected if your FMC runs any of the listed versions AND you use Object Groups for ACLs with high-availability FTD devices, and you observe ACL bypass after reboots.

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 Cisco-provided patches for FMC when available. In the interim, avoid using Object Groups for ACLs in high-availability FTD deployments or manually verify ACL deployment and functionality after any reboot of affected devices.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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