FortiportalApplication · Fortinet
CVE-2017-7337
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 improper Access Control vulnerability in Fortinet FortiPortal versions 4.0.0 and below allows an attacker to interact with unauthorized VDOMs or enumerate other ADOMs via another user's stolen session and CSRF tokens or the adomName parameter in the /fpc/sec/customer/policy/getAdomVersion request.
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 confidenceAn improper access control vulnerability in FortiPortal versions 4.0.0 and below allows attackers to interact with unauthorized VDOMs or enumerate ADOMs by manipulating the adomName parameter in the /fpc/sec/customer/policy/getAdomVersion request or by exploiting stolen session and CSRF tokens.
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
FortiportalApplication
<= 4.0.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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 FortiPortal versionLog into the FortiPortal admin interface and navigate to System > Settings > About, or use the CLI command 'get system status' to retrieve the installed version number.Affected if The installed version is 4.0.0 or lower.
-
Confirm web interface exposureVerify that FortiPortal web interface (HTTPS on port 443 by default) is accessible from network locations where untrusted users could reach it.Affected if The /fpc/sec/customer/policy/getAdomVersion endpoint is reachable from untrusted networks without additional authentication barriers.
-
Inspect session token handlingReview session management configuration in FortiPortal under System > Administration > Security Fabric or equivalent session settings to verify if session tokens are properly bound to user identity and IP.Affected if Session tokens can be reused across different IP addresses or user identities without re-authentication.
-
Test adomName parameter authorizationSend a crafted HTTP request to /fpc/sec/customer/policy/getAdomVersion with an adomName parameter value for an ADOM the authenticated user should not have access to, and observe if the system returns sensitive information.Affected if The response reveals information about ADOMs or VDOMs that the current user is not authorized to access.
A user is affected if their FortiPortal version is 4.0.0 or below and the web interface allows manipulation of the adomName parameter to access unauthorized ADOM/VDOM data.
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 FortiPortal to a version above 4.0.0. Until then, enforce strict session validation and implement proper authorization checks on the adomName parameter to prevent unauthorized VDOM/ADOM access.
Fix this in Fortiportal
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7337 — 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-2017-7337 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