CVE-2021-38121 is a high severity flaw in NetIQ Advanced Authentication, scored 8.3 by NVD. A weak TLS protocol version is accepted in client and server communication when a specific service is reached. It affects versions before 6.3.5.1, and the vendor fixed it in 6.3 Service Pack 5 Patch 1.
What's affected
The record describes insufficient or weak TLS protocol version handling in the communication between Advanced Authentication clients and the server, when a specific service is accessed between devices. It affects versions before 6.3.5.1. The vector is CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L: an adjacent network attacker, low complexity, a low privilege account, user interaction and a changed scope. The adjacent network requirement is why this scores 8.3 rather than higher.
The fixed release is Advanced Authentication 6.3 Service Pack 5 Patch 1, which the record calls 6.3.5.1. The vendor's release notes, dated September 2021, list CVE-2021-38121 among the security fixes and point to knowledge base article KM000033424 for details. The record's product list names 6.3 and 6.3 SP1 explicitly, with a version range of everything before 6.3.5.1.
The record and the release notes agree on the fix version. Neither gives a vendor severity score in the pages I read, so the CVSS number here is the NVD one.
Weakness class: CWE-326.
How to check if you're exposed
There is no package manager command for this one. Advanced Authentication is a self-hosted authentication server, so the check is a version comparison.
Open the administration portal, read the installed version, and compare it with 6.3 Service Pack 5 Patch 1. Anything older than that patch level is in range. If you run several appliances or sites, repeat the check on each one, because they can drift apart.
Then open KM000033424 in the vendor's knowledge base for the product behaviour specific to this CVE. I could not load that article, so I am not summarising it here.
What to do now
- List every Advanced Authentication server and note its installed version.
- Schedule the upgrade to 6.3 Service Pack 5 Patch 1 or any later release you are entitled to.
- Read the vendor release notes before upgrading, since the same patch also resolves other security issues and adds features.
- After the upgrade, test the TLS versions the client facing endpoints accept and turn off anything below your standard.
Why it matters
Weak protocol versions matter because they let an attacker on the network path push a connection down to a version with known cryptographic flaws, then read or alter traffic that was supposed to be protected. On an authentication system that traffic can include credentials and tokens.
The record files this under CWE-326, inadequate encryption strength. The lesson is general: a server should refuse old TLS versions outright rather than negotiate them for compatibility, and clients should pin a minimum version too. Compatibility settings that were reasonable years ago become the weak link later.
After upgrading, it is worth testing from a scanner what TLS versions each Advanced Authentication endpoint still accepts, including the service named in the advisory, instead of assuming the patch settled everything.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Quick check
Why is the score high if the attacker must be on the same network?
The record's vector gives adjacent network access, but the confidentiality and integrity impacts are high and the scope changes, so the overall score is 8.3.
How do I confirm the fix?
Upgrade to 6.3 Service Pack 5 Patch 1 or later, then test which TLS versions the affected endpoints accept. The release notes list the CVE as resolved but do not describe the technical change.
Sources
Last reviewed: 19 October 2026.