dbcve.org
FortiportalApplication · Fortinet

CVE-2024-23105

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to after 7.0.6 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A Use Of Less Trusted Source [CWE-348] vulnerability in Fortinet FortiPortal version 7.0.0 through 7.0.6 and version 7.2.0 through 7.2.1 allows an unauthenticated attack to bypass IP protection through crafted HTTP or HTTPS 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 confidence

Fortinet FortiPortal versions 7.0.0-7.0.6 and 7.2.0-7.2.1 contain a CWE-348 (Use of Less Trusted Source) vulnerability allowing unauthenticated attackers to bypass IP-based access controls via crafted HTTP/HTTPS packets. This could permit unauthorized access to protected resources or administrative interfaces that rely on IP allowlisting for security.

MitigationApply vendor-supplied patches (upgrade to FortiPortal 7.0.7 or 7.2.2 or later) to remediate this vulnerability. Review IP access control policies and monitor for unauthorized access attempts until the patch is applied.

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
Affected:>= 7.0.0, <= 7.0.6= 7.2.0= 7.2.1

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FortiPortal installation
    Locate FortiPortal by checking for the service process (fortiportal) or reviewing installed software on the host. Common installation paths include /opt/fortinet/fortiportal/ or C:\Program Files\Fortinet\FortiPortal\
    Affected if FortiPortal is present on the system
  2. Determine installed version
    Run the command 'fortiportal -version' or check the version file typically located at /opt/fortinet/fortiportal/etc/VERSION in Linux installations, or check the FortiPortal admin web UI under System > Settings > About
    Affected if Version is 7.0.0 through 7.0.6, or exactly 7.2.0 or 7.2.1
  3. Identify IP access control configuration
    Review FortiPortal configuration files for IP allowlisting settings. Check the admin web UI under System > Administrators and IP Policies, or inspect the configuration database for entries matching 'ip-access' or 'allowlist' patterns
    Affected if IP-based access control policies or allowlists are configured for admin interfaces or protected resources
  4. Assess interface exposure
    Review network configuration to determine if the FortiPortal admin or API interfaces are accessible from untrusted networks. Check firewall rules and reverse proxy configurations exposing port 443 or 80
    Affected if Management or admin interfaces are reachable from external or untrusted networks without additional authentication barriers

You are affected if FortiPortal version 7.0.0-7.0.6 or 7.2.0-7.2.1 is installed AND IP-based access controls are configured on exposed interfaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 7.0.6
Interim mitigation

Apply vendor-supplied patches (upgrade to FortiPortal 7.0.7 or 7.2.2 or later) to remediate this vulnerability. Review IP access control policies and monitor for unauthorized access attempts until the patch is applied.

Recommended fix Moderate confidence

FortiPortal 7.0.7 or 7.2.2 (or later stable releases in respective branches)

  1. 1. Identify the current FortiPortal version running in your environment
  2. 2. If running version 7.0.0-7.0.6, upgrade to version 7.0.7 or later
  3. 3. If running version 7.2.0 or 7.2.1, upgrade to version 7.2.2 or later
  4. 4. After upgrade, verify that IP protection mechanisms are functioning correctly
  5. 5. Test that legitimate traffic is not blocked after the upgrade
Caveat Review release notes for any configuration or feature changes between affected and fixed versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiportal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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