FortipresenceApplication · Fortinet
CVE-2023-27998
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 lack of custom error pages vulnerability [CWE-756] in FortiPresence versions 1.2.0 through 1.2.1 and all versions of 1.1 and 1.0 may allow an unauthenticated attacker with the ability to navigate to the login GUI to gain sensitive information via navigating to specific HTTP(s) paths.
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 confidenceThis is an information disclosure vulnerability in FortiPresence where the lack of custom error pages allows unauthenticated attackers accessing the login GUI to obtain sensitive information by navigating to specific HTTP(S) paths. The default error responses reveal system details, paths, or configuration information that should not be exposed.
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
FortipresenceApplication
= 1.0.0= 1.1.0= 1.1.1= 1.2.0= 1.2.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm FortiPresence is exposedIdentify if FortiPresence login GUI is accessible from the network by accessing the login page via HTTP(S) to the affected hostAffected if FortiPresence GUI is accessible without authentication and reveals version or system details in error responses
-
Check installed FortiPresence versionLog into the FortiPresence admin interface or check the system information page within the product to identify the exact version numberAffected if The installed version matches 1.0.0, 1.1.0, 1.1.1, 1.2.0, or 1.2.1
-
Test for information disclosure via error pagesNavigate to non-existent or invalid HTTP(S) paths on the FortiPresence login GUI (such as /invalidpath or /../) and observe the error responseAffected if The default error response reveals system paths, version details, stack traces, or internal configuration information rather than a generic message
-
Check if custom error pages are configuredReview FortiPresence server configuration or error handling settings to determine whether custom error pages that return generic responses are enabledAffected if Custom error pages are NOT configured and the system returns default error messages exposing sensitive information
You are affected if FortiPresence version 1.0.0 through 1.2.1 is running with its login GUI accessible and default error pages are in use (not replaced with custom generic error pages).
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 FortiPresence to a version beyond 1.2.1 (once available) or implement custom error pages that return generic responses without exposing system paths, version details, or stack traces.
Fix this in Fortipresence
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-2023-27998 — 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-2023-27998 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