High severity · published Aug 28, 2024
CVE-2021-38121
Insufficient or weak TLS protocol version identified in Advance authentication client server communication when specific service is accessed between devices. This issue affects…
8.8
CVSS
0.2%
EPSS
No
On KEV
Description
Insufficient or weak TLS protocol version identified in Advance authentication client server communication when specific service is accessed between devices. This issue affects NetIQ Advance Authentication versions before 6.3.5.1
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 8% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
NA
Netiq Advanced Authentication · Microfocus
before 6.3; 6.3; 6.3; 6.3; 6.3; 6.3; +2 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2021-38121
CVE.org
https://www.cve.org/CVERecord?id=CVE-2021-38121
Release Notes
https://www.netiq.com/documentation/advanced-authentication-63/advanced-authentication-releasenotes-6351/data/advanced-authentication-releasenotes-6351.html
More from Netiq Advanced Authentication
9.9
CVE-2021-22530
A vulnerability identified in NetIQ Advance Authentication that doesn't enforce account lockout when brute force attack is performed on API based login
9.8
CVE-2023-24468
Broken access control in Advanced Authentication versions prior to 6.4.1.1 and 6.3.7.2
8.2
CVE-2021-38122
A Cross-Site Scripting vulnerable identified in NetIQ Advance Authentication that impacts the server functionality and disclose sensitive information
7.2
CVE-2021-38120
A vulnerability identified in Advance Authentication that allows bash command Injection in administrative controlled functionality of backup due to improper handling in…
7.2
CVE-2021-22497
Advanced Authentication versions prior to 6.3 SP4 have a potential broken authentication due to improper session management issue