dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-39340

HIGH · 8.8 CVSS v3.1 Published 2024-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
The authentication system of Securepoint UTM mishandles OTP keys. This allows the bypassing of second-factor verification (when OTP is enabled) in both the administration web interface and the user portal. Affected versions include UTM 11.5 through 12.6.4 and Reseller Preview 12.7.0. The issue has been fixed in UTM 12.6.5 and 12.7.1.

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 · moderate confidence

The Securepoint UTM authentication system contains a flaw in how it handles OTP (One-Time Password) keys, allowing attackers to bypass second-factor verification. This authentication bypass affects both the administration web interface and the user portal when OTP is enabled.

MitigationUpgrade Securepoint UTM to version 12.6.5 or 12.7.1 (or later) to obtain the patched authentication handling. Until patched, monitor for unauthorized access attempts and consider additional compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Securepoint UTM installation
    Identify if the target system is running Securepoint UTM. Check system documentation, product branding, or run: `dpkg -l | grep -i securepoint` or `rpm -qa | grep -i securepoint` on the UTM appliance.
    Affected if System is not running Securepoint UTM product
  2. Check installed UTM version
    Run: `spUI --version` or check the admin web interface dashboard for the firmware version. Compare against the fixed versions 12.6.5 and 12.7.1.
    Affected if Installed version is lower than 12.6.5 or 12.7.1 (e.g., 12.x versions before these release points)
  3. Verify OTP is enabled for admin interface
    Log into the Securepoint UTM admin web interface. Navigate to: Administration > Authentication > OTP Settings (or similar path). Check if OTP/2FA is enabled for administrative logins.
    Affected if OTP is enabled for admin authentication (vulnerability only applies when OTP is active)
  4. Verify OTP is enabled for user portal
    Log into the Securepoint UTM admin web interface. Navigate to: User Management > Portal Settings > Two-Factor Authentication. Check if OTP is enabled for the user portal.
    Affected if OTP is enabled for user portal access

User is affected if running Securepoint UTM version below 12.6.5 or 12.7.1 AND OTP authentication is enabled for either the admin interface or user portal.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Securepoint UTM to version 12.6.5 or 12.7.1 (or later) to obtain the patched authentication handling. Until patched, monitor for unauthorized access attempts and consider additional compensating controls.

Recommended fix High confidence

UTM 12.6.5 or UTM 12.7.1 (depending on current branch)

  1. 1. Back up the current UTM configuration and all critical data before proceeding with the upgrade.
  2. 2. Verify the current UTM version by accessing the administration web interface or using the CLI.
  3. 3. Download the appropriate upgrade image (UTM 12.6.5 for systems on 12.x branch, or UTM 12.7.1 for systems on 12.7 branch) from the official Securepoint download portal.
  4. 4. Upload the upgrade image through the UTM administration interface (System > Update > Upload) or via CLI using the firmware update command.
  5. 5. Initiate the firmware upgrade and allow the system to reboot automatically.
  6. 6. After reboot, verify the new version is installed and confirm OTP authentication is functioning correctly by testing login with second-factor verification.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39340 — 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-39340 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