FortimanagerApplication · Fortinet
CVE-2024-35277
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 missing authentication for critical function in Fortinet FortiPortal version 6.0.0 through 6.0.15, FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, 7.0.0 through 7.0.12, 6.4.0 through 6.4.14 allows attacker to access to the configuration of the managed devices by sending specifically crafted packets
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 missing authentication vulnerability in FortiPortal (6.0.0-6.0.15) and FortiManager (6.4.0-6.4.14, 7.0.0-7.0.12, 7.2.0-7.2.5, 7.4.0-7.4.2) allows unauthenticated attackers to access the configuration of managed devices by sending specifically crafted packets. This is a CWE-306 (Missing Authentication for Critical Function) vulnerability exploitable over the network without user interaction or privileges.
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
>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.6>= 7.4.0, < 7.4.3
Fortimanager CloudApplication
>= 7.0.1, < 7.0.13>= 7.2.1, < 7.2.7>= 7.4.1, < 7.4.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if FortiManager is installedCheck for FortiManager processes or services running on the system. On Linux, run 'ps -ef | grep -i fortimanager' or check for /opt/fortimanager directory. On Windows, check services for FortiManager entries.Affected if FortiManager is found running on the system
-
Determine FortiManager versionAccess the FortiManager CLI and run 'get system status' or 'fortimanager -v' to retrieve the installed version number.Affected if Version matches any of these ranges: 6.4.0-6.4.14, 7.0.0-7.0.12, 7.2.0-7.2.5, 7.4.0-7.4.2 (or corresponding FortiManager Cloud versions: 7.0.1-7.0.12, 7.2.1-7.2.6, 7.4.1-7.4.2)
-
Identify if FortiPortal is installedCheck for FortiPortal processes or services. Look for /opt/fortiportal directory or run 'ps -ef | grep -i fortiportal'. Check if port 443 or 80 is serving FortiPortal web interface.Affected if FortiPortal is found running on the system
-
Determine FortiPortal versionLog into FortiPortal web interface and navigate to System > Settings > About, or use CLI command 'fortiportal -v' to check the version.Affected if Version is 6.0.0 through 6.0.15
You are affected if either FortiManager (versions 6.4.0-6.4.14, 7.0.0-7.0.12, 7.2.0-7.2.5, or 7.4.0-7.4.2) or FortiPortal (versions 6.0.0-6.0.15) is installed and running in your environment, as these versions lack authentication for critical configuration access functions.
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 · scoped6.4.157.0.137.2.6
Apply Fortinet vendor patches to upgrade FortiPortal and FortiManager to patched versions that address the missing authentication vulnerability.
FortiManager: 6.4.15, 7.0.13, 7.2.6, or 7.4.3 | FortiManager Cloud: 7.0.13, 7.2.7, or 7.4.3
- Identify the current FortiManager or FortiManager Cloud version using the web UI or CLI command 'get system status'
- Review the release notes for the target fixed version before upgrading
- Plan a maintenance window and ensure backups of the FortiManager configuration are created
- For FortiManager: upgrade to version 6.4.15, 7.0.13, 7.2.6, or 7.4.3 depending on your current major branch
- For FortiManager Cloud: upgrade to version 7.0.13, 7.2.7, or 7.4.3 depending on your current major branch
- If upgrading across major versions (e.g., 6.4 to 7.0), follow Fortinet's upgrade path documentation and test in a non-production environment first
- After upgrade, verify the version using 'get system status' and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35277 — 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-35277 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