Security readout for executives and security teams
Plain-English summary
CVE-2021-45925 lets an unauthenticated network attacker tell whether guessed usernames exist during login to affected Lanner BMC firmware. It does not directly grant access, but it reduces uncertainty for password attacks against management interfaces.
Executive priority
Treat this as a near-term hardening item, especially for exposed management networks. It is not a standalone takeover issue, but BMC accounts are high-value and username disclosure can support broader compromise attempts.
Technical view
The issue is CWE-203 observable discrepancy in the login process for Lanner IAC-AST2500A standard firmware 1.10.0. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, low confidentiality impact only.
Likely exposure
Exposure is most likely where Lanner IAC-AST2500A BMC interfaces running standard firmware 1.10.0 are reachable from administrative, enterprise, vendor, or internet-facing networks.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. The risk is mainly as an aid to credential guessing, phishing targeting, or follow-on attacks against BMC accounts.
Researcher notes
Evidence is limited to the named product and firmware version. No source in the bundle names a patch, workaround, affected CPE, or exploit activity. Avoid extending impact beyond username enumeration without vendor confirmation.
Mitigation direction
- Inventory Lanner IAC-AST2500A BMC firmware versions.
- Check Lanner and Nozomi guidance for fixed firmware or mitigations.
- Restrict BMC management access to trusted administration networks.
- Enforce strong authentication and monitor failed login patterns.
- Remove internet exposure for affected BMC login interfaces.
Validation and detection
- Confirm whether deployed devices run standard firmware 1.10.0.
- Verify BMC login interfaces are not reachable from untrusted networks.
- Review authentication logs for username guessing indicators.
- Check vendor guidance for patched or replacement firmware status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCVE-2021-45925 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.