LiveActive security incident?Get immediate response
CVE Record

CVE-2021-45890: basic/BasicAuthProvider.java in AuthGuard before 0.9.0 allows authentication via an inactive identifier.

basic/BasicAuthProvider.java in AuthGuard before 0.9.0 allows authentication via an inactive identifier.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

AuthGuard before 0.9.0 could accept authentication tied to an inactive identifier. In practical terms, an account or identifier expected to be disabled might still be usable. The public record does not provide CVSS scoring, affected CPEs, or evidence of active exploitation.

Executive priority

Treat this as a targeted authentication-control risk, not a confirmed widespread emergency. Prioritize if AuthGuard is used in internet-facing, administrative, or privileged systems; otherwise handle through normal dependency remediation.

Technical view

The CVE describes a flaw in AuthGuard basic/BasicAuthProvider.java where authentication could succeed through an inactive identifier. References point to GitHub issue 166, pull request 181, commit 9783b114, and the v0.8.0 to v0.9.0 comparison. No CWE or CVSS vector is provided.

Likely exposure

Exposure appears limited to systems using AuthGuard before 0.9.0, especially where BasicAuthProvider is enabled and inactive identifiers are used for access control. The source bundle does not identify downstream products, CPEs, or hosted services.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The issue is authentication-related, so business impact depends on whether inactive identifiers map to real users, service accounts, or privileged access.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, exploit status, or detailed advisory is included. Analysis should stay anchored to AuthGuard before 0.9.0 and the linked GitHub change history.

Mitigation direction

  • Inventory applications and dependencies for AuthGuard versions before 0.9.0.
  • Upgrade AuthGuard to 0.9.0 or later after compatibility testing.
  • Confirm BasicAuthProvider usage and disable it where unnecessary.
  • Review vendor or project guidance before applying compensating controls.
  • Audit inactive identifiers and remove stale authentication material.

Validation and detection

  • Check dependency manifests and deployed artifacts for AuthGuard version numbers.
  • Identify whether BasicAuthProvider is present in production authentication paths.
  • Review logs for successful authentication by inactive identifiers.
  • In staging, confirm inactive identifiers cannot authenticate.
  • Document affected services and remediation status for tracking.
Prepared
Confidence
medium
Sources
6

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.

cve · low confidence lookup

CVE-2021-45890 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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