CVE-2024-8891
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 · uneditedAn attacker with no knowledge of the current users in the web application, could build a dictionary of potential users and check the server responses as it indicates whether or not the user is present in CIRCUTOR Q-SMT in its firmware version 1.0.4.
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 confidenceCIRCUTOR Q-SMT firmware 1.0.4 contains a user enumeration vulnerability where the web application returns distinguishable server responses that reveal whether a given username exists in the system. An unauthenticated attacker can use this to compile a list of valid user accounts by testing usernames against the authentication endpoints.
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.0.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 the installed firmware versionAccess the Circutor Q-SMT web interface and navigate to the system information or firmware version page, typically found in the admin or settings section. Alternatively, check the login page footer or banner for version information.Affected if The firmware version displayed is exactly 1.0.4
-
Confirm the web application is accessibleAttempt to access the Circutor Q-SMT login page via HTTP/HTTPS using a web browser or curl command to the device IP address.Affected if The web application login page loads and is reachable over the network
-
Test authentication response for invalid usernameSend a POST request to the authentication endpoint (typically /login or similar) with a known-invalid username such as 'nonexistentuser123' and a password. Capture the HTTP response status code and message.Affected if The server returns a specific error message indicating the username does not exist or is invalid
-
Test authentication response for valid usernameSend a POST request to the same authentication endpoint with a guessed or common username such as 'admin' and any password. Capture the response.Affected if The server returns a different response (such as 'invalid password' versus 'invalid username') indicating the username is valid but the password is wrong, or the response time differs noticeably
-
Compare response differencesCompare the HTTP responses, error messages, and response timing between valid and invalid username attempts. Document whether an attacker could distinguish valid accounts from invalid ones.Affected if The responses are measurably different in content, error message text, or timing, allowing user enumeration
The environment is affected if running Circutor Q-SMT firmware version 1.0.4 and the web authentication endpoints return distinguishable responses for valid versus invalid usernames.
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 dataModify the authentication mechanism to return identical HTTP responses (including error messages and timing) for both valid and invalid usernames to prevent user enumeration.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8891 — 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-2024-8891 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