Description
SEP sesam before 5.2.0.24 mishandles User Authorization with MFA. If AD authentication is configured and MFA is enforced, an attacker can create a second OTP access capability. SEP sesam and Active Directory handle username capitalization differently, which may allow multiple SEP sesam user accounts to be created for the same Active Directory (AD) account. Active Directory treats usernames as case-insensitive, while SEP sesam distinguishes between different letter casing. As a result, the same AD user can be represented by multiple SEP sesam user accounts that differ only in username capitalization. When Active Directory authentication is configured and multi-factor authentication (MFA) is enforced, this behavior may allow an additional OTP Authenticator to be registered for the same AD account, reducing the effectiveness of MFA protection.
Published: 2026-09-12
Score: 3.5 Low
EPSS: < 1% Very Low
KEV: No
Impact: MFA bypass leading to reduced authentication strength
Action: Patch
AI Analysis

Impact

SEP sesam before 5.2.0.24 mishandles system treats usernames case-sensitive while Active Directory is case-insensitive, allowing an attacker to create multiple SEP sesam accounts that map to the same AD account, and register an additional One Time Password authenticator for that account, thereby weakening the MFA protection. The underlying weakness is identified as CWE-180, which describes improper handling of value comparison and normalization.

Affected Systems

All SEP sesam deployments using version <5.2.0.24 with Active Directory authentication and enforce MFA. The flaw is specific to environments where usernames are compared without normalizing the case, causing duplicate symbolic accounts for a single AD account.

Risk and Exploitability

The CVSS score of 3.5 indicates moderate severity. The EPSS score is below 1%, indicating very low current exploitation probability. The vulnerability is not listed in CISA KEV catalog, suggesting no publicly known exploit. The risk remains moderate primarily in environments where MFA is the main defense, as the flaw allows reduction of MFA effectiveness.

Generated by OpenCVE AI on September 15, 2026 at 17:49 UTC.

Remediation

Vendor Solution

The issue is fixed in latest release versions >= v5.2.0.24. It is strongly recommended to update, if AD authentication is in use.


OpenCVE Recommended Actions

  • Update SEP sesam to v5.2.0.24 or later.
  • Configure SEP sesam to perform case-insensitive username comparison or align with AD’s handling.
  • Audit existing user accounts for duplicates based on case differences and remove or merge redundant accounts.

Generated by OpenCVE AI on September 15, 2026 at 17:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 15 Sep 2026 18:15:00 +0000

Type Values Removed Values Added
Title Case-sensitive Username Handling Enables Duplicate MFA Authenticators in SEP sesam

Tue, 15 Sep 2026 03:00:00 +0000

Type Values Removed Values Added
Title MFA Bypass via Username Case Sensitivity in SEP sesam

Mon, 14 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
Title MFA Bypass via Username Case Sensitivity in SEP sesam
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 14 Sep 2026 06:15:00 +0000

Type Values Removed Values Added
Title Multiple SEP sesam User Accounts via Case Sensitivity Allowing Extra MFA Factor

Sun, 13 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
Title Multiple SEP sesam User Accounts via Case Sensitivity Allowing Extra MFA Factor

Sun, 13 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
First Time appeared Sep
Sep sesam
Vendors & Products Sep
Sep sesam

Sun, 13 Sep 2026 14:15:00 +0000

Type Values Removed Values Added
Title SEP sesam MFA Bypass via Username Case Handling

Sun, 13 Sep 2026 00:00:00 +0000

Type Values Removed Values Added
Title SEP sesam MFA Bypass via Username Case Handling

Sat, 12 Sep 2026 22:30:00 +0000

Type Values Removed Values Added
Description SEP sesam before 5.2.0.24 mishandles User Authorization with MFA. If AD authentication is configured and MFA is enforced, an attacker can create a second OTP access capability. SEP sesam and Active Directory handle username capitalization differently, which may allow multiple SEP sesam user accounts to be created for the same Active Directory (AD) account. Active Directory treats usernames as case-insensitive, while SEP sesam distinguishes between different letter casing. As a result, the same AD user can be represented by multiple SEP sesam user accounts that differ only in username capitalization. When Active Directory authentication is configured and multi-factor authentication (MFA) is enforced, this behavior may allow an additional OTP Authenticator to be registered for the same AD account, reducing the effectiveness of MFA protection.
Weaknesses CWE-180
References
Metrics cvssV3_1

{'score': 3.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-09-14T16:22:53.589Z

Reserved: 2026-08-25T06:14:33.619Z

Link: CVE-2026-79300

cve-icon Vulnrichment

Updated: 2026-09-14T16:22:47.936Z

cve-icon NVD

Status : Deferred

Published: 2026-09-12T23:17:00.893

Modified: 2026-09-22T20:00:03.713

Link: CVE-2026-79300

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-15T18:00:17Z

Weaknesses
  • CWE-180

    Incorrect Behavior Order: Validate Before Canonicalize