CyberRota Analysis
AI-GeneratedSEP sesam versions prior to 5.2.0.24 are vulnerable due to improper handling of user authorization with multi-factor authentication (MFA), allowing attackers to create multiple user accounts linked to the same Active Directory account by exploiting case sensitivity differences. This flaw can lead to the registration of an additional OTP Authenticator for the same user, undermining the intended security of MFA. Organizations using SEP sesam with Active Directory authentication should prioritize addressing this vulnerability to enhance their security posture.
Original NVD 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.