FortianalyzerApplication · Fortinet
CVE-2024-21757
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 unverified password change in Fortinet FortiManager versions 7.0.0 through 7.0.10, versions 7.2.0 through 7.2.4, and versions 7.4.0 through 7.4.1, as well as Fortinet FortiAnalyzer versions 7.0.0 through 7.0.10, versions 7.2.0 through 7.2.4, and versions 7.4.0 through 7.4.1, allows an attacker to modify admin passwords via the device configuration backup.
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 confidenceUnverified password change vulnerability in FortiManager and FortiAnalyzer allows attackers to modify admin passwords through device configuration backup without proper authentication verification.
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
FortianalyzerApplication
>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.2
FortimanagerApplication
>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiManager or FortiAnalyzer versionRun 'get system status' or 'fnsysctl get system status' on the CLI to retrieve the firmware versionAffected if The version falls within 7.0.0-7.0.10, 7.2.0-7.2.4, or 7.4.0-7.4.1
-
Confirm product typeFrom the system status output, verify whether the device is FortiManager or FortiAnalyzerAffected if The product is either FortiManager or FortiAnalyzer with an affected version
-
Verify admin account configurationRun 'get admin user' or 'show system admin' to list admin accounts defined on the deviceAffected if Admin accounts exist on the system (the vulnerability allows unauthorized password modification of these accounts)
-
Check for unauthorized password changes in logsRun 'execute log filter category 1' then 'execute log display' to review event logs for password modification eventsAffected if Password change events appear in logs without corresponding legitimate admin sessions
You are affected if your FortiManager or FortiAnalyzer runs version 7.0.0-7.0.10, 7.2.0-7.2.4, or 7.4.0-7.4.1 and has admin 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.117.2.57.4.2
Update to FortiManager/FortiAnalyzer versions 7.0.11/7.2.5/7.4.2 or later to patch the vulnerability.
FortiManager/FortiAnalyzer 7.0.11, 7.2.5, or 7.4.2 depending on your current branch
- 1. Backup the FortiManager/FortiAnalyzer configuration and data before upgrading
- 2. Download the appropriate firmware for your version branch from Fortinet support portal: 7.0.11, 7.2.5, or 7.4.2
- 3. Upload the firmware file through the FortiManager/FortiAnalyzer web UI (System > Firmware) or CLI
- 4. Initiate the firmware upgrade and allow the system to reboot
- 5. After reboot, verify the firmware version matches the expected fixed version
- 6. Verify admin user configuration and passwords are intact
- 7. Confirm normal operation of managed devices and logging functions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortianalyzer
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21757 — 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-21757 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