Safeguard
Vulnerability Analysis•

CVE-2021-22530: High Missing Lockout in NetIQ Advanced Authentication

CVE-2021-22530 is a missing account lockout on API logins in NetIQ Advanced Authentication before 6.3.5.1. Update to 6.3 SP5 Patch 1 or later.

Safeguard Security Team
3 min read

CVE-2021-22530 is a high severity (CVSS 8.2) flaw in NetIQ Advanced Authentication, where account lockout is not enforced on API based logins, so brute force attempts can continue. All versions before 6.3.5.1 are affected. The vendor release notes list the fix in 6.3 Service Pack 5 Patch 1.

What's affected

  • NetIQ Advanced Authentication (now OpenText), all versions before 6.3.5.1, per the NVD record. The record lists 6.3 and 6.3 SP1 among the products.
  • Fixed in Advanced Authentication 6.3 Service Pack 5 Patch 1 (release notes dated September 2021), which lists this CVE among the security fixes.
  • The impact is possible account compromise, or degraded server performance from sustained guessing.
  • The vector needs a low privilege account and user interaction, with a changed scope.
  • KEV status: false.

How to check if you're exposed

Open the Advanced Authentication administration portal and check the product version. Anything older than 6.3.5.1 is affected. If you are unsure, the release notes name SP5 Patch 1 as the version carrying the fix.

Also review authentication logs for large runs of failed API logins against single accounts, which is the behavior this flaw allows to continue unchecked.

What to do now

  1. Plan an upgrade to Advanced Authentication 6.3 SP5 Patch 1 or later and test it in a staging environment.
  2. Read the vendor knowledge article for CVE-2021-22530 (KM000033422, named in the release notes) for specific guidance.
  3. Until you upgrade, monitor API login failures and alert on repeated failures per account or source address.
  4. Add network level rate limiting in front of the authentication API if you have a gateway that supports it.
  5. Check that strong multi factor methods are enforced, so a guessed password alone is not enough.

Why it matters

The record lists CWE-307, improper restriction of excessive authentication attempts, and CWE-667, improper locking. The usual defense against password guessing is to lock or slow an account after repeated failures. Here, the API login path did not apply that control, so the protection that worked on one interface was missing on another.

This is a pattern worth checking in any system with more than one way to log in. A web form, a mobile endpoint and an API may each need their own limits. Attackers will test the least protected one.

Quick check

Which release fixes it?

The vendor release notes list the fix in Advanced Authentication 6.3 Service Pack 5 Patch 1, which matches the record saying versions before 6.3.5.1 are affected.

Can multi factor authentication help while I plan the upgrade?

It reduces the value of a guessed password, but it does not stop the guessing load itself. Combine it with monitoring and rate limits.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.