Secure Firewall Management CenterApplication · Cisco
CVE-2024-20482
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 · uneditedA vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software, formerly Firepower Management Center Software, could allow an authenticated, remote attacker to elevate privileges on an affected device. To exploit this vulnerability, an attacker must have a valid account on the device that is configured with a custom read-only role. This vulnerability is due to insufficient validation of role permissions in part of the web-based management interface. An attacker could exploit this vulnerability by performing a write operation on the affected part of the web-based management interface. A successful exploit could allow the attacker to modify certain parts of the configuration.
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 · moderate confidenceThis is a privilege escalation vulnerability in Cisco Secure Firewall Management Center (FMC). An authenticated attacker with a custom read-only role can bypass role restrictions in the web-based management interface due to insufficient validation of role permissions, allowing write operations that should be denied and modification of certain device configurations.
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
= 7.2.0= 7.2.0.1= 7.2.1= 7.2.2= 7.2.3= 7.2.3.1= 7.2.4= 7.2.4.1= 7.2.5= 7.2.5.1= 7.2.5.2= 7.2.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FMC software versionLog into the FMC web interface and navigate to System > About, or run 'show version' via CLI to confirm the installed FMC versionAffected if The installed version matches 7.2.0, 7.2.0.1, 7.2.1, 7.2.2, 7.2.3, 7.2.3.1, 7.2.4, 7.2.4.1, 7.2.5, 7.2.5.1, 7.2.5.2, or 7.2.6
-
Review custom user rolesIn the FMC web interface, go to System > Users > Roles to list all custom roles defined in the systemAffected if Any custom roles with read-only permissions are defined in the system
-
Check for role assignments to usersNavigate to System > Users > Users and examine which users are assigned to custom read-only rolesAffected if Any authenticated users are assigned custom read-only roles
-
Audit recent configuration changesReview the FMC audit logs (System > Audit Log) and look for write operations or device configuration modifications performed by users with read-only rolesAffected if Configuration changes were made by users assigned read-only or custom read-only roles
-
Inspect role permission settingsExamine the specific permissions granted to custom roles in System > Users > Roles, focusing on whether write operations are explicitly denied for device configurationsAffected if Custom read-only roles exist but may allow write operations on certain device configurations
You are affected if your FMC runs version 7.2.0 through 7.2.6 and you have users assigned to custom read-only roles that may have performed unauthorized configuration changes.
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.
From vendor dataApply the Cisco patch/softwar update for FMC when available. Until then, limit custom read-only role assignments and monitor for unauthorized configuration changes.
Fix this in Secure Firewall Management Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20482 — 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-2024-20482 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