LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22530: Improper account management vulnerability in NetIQ Advance Authentication

A vulnerability identified in NetIQ Advance Authentication that doesn't enforce account lockout when brute force attack is performed on API based login. This issue may lead to user account compromise if successful or may impact server performance. This issue impacts all NetIQ Advance Authentication before 6.3.5.1

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-22530 is an account lockout weakness in NetIQ Advance Authentication. API-based login attempts may not be locked out during brute-force activity, creating a path to account compromise and possible server performance impact. The source states versions before 6.3.5.1 are affected.

Executive priority

Treat as a high-priority remediation for identity infrastructure. It can affect account protection controls and may support credential compromise attempts, especially if API login endpoints are broadly reachable.

Technical view

The issue is improper account management around API login lockout enforcement during brute-force attempts. CVSS 3.1 score is 8.2 high, with network attack vector, low complexity, changed scope, high confidentiality impact, and low integrity and availability impacts. CWE is listed as CWE-667.

Likely exposure

Organizations using NetIQ Advance Authentication versions earlier than 6.3.5.1 are the likely exposed population. Exposure is higher where API login endpoints are reachable by untrusted networks or high-volume authentication attempts.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is credible because the weakness affects API login lockout behavior, which can enable repeated credential attempts and performance degradation.

Researcher notes

Evidence is limited to the CVE record and NetIQ 6.3.5.1 release reference. Do not infer exploit availability. Focus validation on version inventory, API login exposure, lockout enforcement, failed-authentication telemetry, and upgrade status.

Mitigation direction

  • Identify all NetIQ Advance Authentication deployments and versions.
  • Upgrade affected deployments to 6.3.5.1 or later per vendor guidance.
  • Restrict API login endpoint exposure to trusted networks where feasible.
  • Review vendor release notes and operational hardening guidance.
  • Monitor authentication endpoints for unusual failed-login volume.

Validation and detection

  • Confirm deployed NetIQ Advance Authentication version is 6.3.5.1 or later.
  • Review authentication logs for repeated API login failures.
  • Verify account lockout policy behavior on supported non-production systems.
  • Check whether API login endpoints are internet-accessible.
  • Confirm monitoring alerts cover brute-force patterns and performance impact.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-22530 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L2.35.3Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2021-22530Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenTextNetIQ Advance Authentication6.3.5.1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.