CVE-2021-44467
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA broken access control vulnerability in the KillDupUsr_func function of spx_restservice allows an attacker to arbitrarily terminate active sessions of other users, causing a Denial-of-Service (DoS) condition, if an input parameter is correctly guessed. This issue affects: Lanner Inc IAC-AST2500A standard firmware version 1.10.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBroken access control vulnerability in the KillDupUsr_func function of spx_restservice allows an unauthenticated attacker to terminate active sessions of other users by correctly guessing an input parameter, causing denial of service. This affects Lanner IAC-AST2500A firmware version 1.10.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify hardware modelCheck the system label, BMC web interface, or IPMI command output for the model number 'IAC-AST2500A' or 'AST2500'Affected if The hardware is not a Lanner IAC-AST2500A device, then it is not affected
-
Check firmware versionAccess the BMC web interface, check IPMI firmware version, or use IPMI command: ipmitool -I open mc info or similar to retrieve firmware versionAffected if Firmware version is not exactly 1.10.0, then it is not affected
-
Verify spx_restservice availabilityCheck if the REST API service (spx_restservice) is accessible on the BMC management interface, typically on port 443 or 80. Attempt to access the API endpoint or check running processes via BMC diagnostics if availableAffected if The spx_restservice is not running or not exposed on the network, the attack surface is reduced but the vulnerability still exists in the firmware if version is 1.10.0
-
Look for session termination eventsReview BMC audit logs, system logs, or authentication logs for unexpected session terminations or repeated 'user logged out' events that could indicate exploitation attemptsAffected if Unexpected mass session terminations are logged from unauthenticated or unknown sources, this indicates active exploitation
You are affected only if you have a Lanner IAC-AST2500A device running firmware version exactly 1.10.0, regardless of whether the spx_restservice is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied firmware patch when available. In the interim, restrict network access to the management interface and implement rate limiting on authentication endpoints to reduce the effectiveness of parameter guessing attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-44467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data