FortiadcApplication · Fortinet
CVE-2021-24024
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 clear text storage of sensitive information into log file vulnerability in FortiADCManager 5.3.0 and below, 5.2.1 and below and FortiADC 5.3.7 and below may allow a remote authenticated attacker to read other local users' password in log files.
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 confidenceFortiADCManager and FortiADC store user passwords in clear text within log files. A remote authenticated attacker with access to the system can read these log files to obtain other local users' passwords in plaintext.
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
FortiadcApplication
<= 5.3.7
Fortiadc ManagerApplication
<= 5.3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check FortiADC versionAccess the FortiADC CLI or GUI and run the command: 'get system status' or navigate to System > FortiView > System Information to view the firmware version.Affected if The version displayed is 5.3.7 or earlier.
-
Check FortiADC Manager versionAccess FortiADC Manager and navigate to the About or System Settings section to view the software version.Affected if The version displayed is 5.3.0 or earlier.
-
Examine log files for plaintext passwordsAccess the system via CLI or GUI and locate log files in /var/log/ or through the Log & Report viewer. Search log entries for plaintext password strings or user credential data.Affected if Log files contain plaintext passwords or credential information in plain text.
-
Verify log file access controlsCheck file permissions on log directories using 'ls -la' or review user access permissions through the FortiADC administrative interface.Affected if Multiple authenticated users have read access to system logs without proper segmentation.
You are affected if your FortiADC version is 5.3.7 or earlier, or FortiADC Manager version is 5.3.0 or earlier, and log files contain plaintext user credentials.
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 dataUpgrade to FortiADCManager 5.4.0 or above, FortiADCManager 5.3.1 or above, or FortiADC 5.4.0 or above. Additionally, restrict access to log files and monitor for unauthorized access.
Fix this in Fortiadc
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24024 — 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-2021-24024 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