FortimanagerApplication · Fortinet
CVE-2024-47571
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 · uneditedAn operation on a resource after expiration or release in Fortinet FortiManager 6.4.12 through 7.4.0 allows an attacker to gain improper access to FortiGate via valid credentials.
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 confidenceA Use of Expired/Released Resource vulnerability (CWE-910) in FortiManager versions 6.4.12 through 7.4.0 allows authenticated attackers to perform operations on resources after expiration or release, enabling improper access to managed FortiGate devices using valid credentials.
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
FortimanagerApplication
>= 7.0.7, < 7.0.9= 6.4.12= 7.2.3= 7.4.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check FortiManager system version via CLIRun the command 'get system status' or 'show system version' in the FortiManager CLI consoleAffected if The displayed version matches 6.4.12, 7.0.7, 7.0.8, 7.2.3, or 7.4.0
-
Check FortiManager version via web UILog into the FortiManager web interface and navigate to System > Settings or the Dashboard, then locate the firmware version displayedAffected if The firmware version shown is one of the affected versions: 6.4.12, 7.0.7, 7.0.8, 7.2.3, or 7.4.0
-
Verify admin accounts existIn the web UI, go to System > Administrator to confirm valid administrator accounts are configuredAffected if Any active administrator accounts are present on the system (the vulnerability is exploitable by attackers with valid credentials)
Your FortiManager is affected if it is running version 6.4.12, 7.0.7, 7.0.8, 7.2.3, or 7.4.0 and has active administrator accounts configured.
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.
dbcve · scoped7.0.9
Upgrade FortiManager to version 7.4.1 or later, 7.2.7 or later, or 6.4.13 or later to remediate this vulnerability.
Upgrade to 7.4.1 or later (or the latest available 7.4.x/7.2.x/7.0.x/6.4.x release for your branch)
- 1. Identify your current FortiManager version from the affected list (6.4.12, 7.0.7, 7.0.8, 7.2.3, or 7.4.0)
- 2. Access FortiManager admin web UI or CLI
- 3. Download the appropriate fixed firmware version from https://support.fortinet.com/ (requires active support contract)
- 4. For version 6.4.12: upgrade to 6.4.13 or later
- 5. For version 7.0.7 or 7.0.8: upgrade to 7.0.9 or later
- 6. For version 7.2.3: upgrade to 7.2.4 or later
- 7. For version 7.4.0: upgrade to 7.4.1 or later
- 8. Backup current FortiManager configuration before upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47571 — 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-47571 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