CVE-2024-8890
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 access to the network where the CIRCUTOR Q-SMT is located in its firmware version 1.0.4, could obtain legitimate credentials or steal sessions due to the fact that the device only implements the HTTP protocol. This fact prevents a secure communication channel from being established.
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 confidenceThe CIRCUTOR Q-SMT firmware version 1.0 only implements unencrypted HTTP communication, lacking HTTPS/TLS support. This allows network-adjacent attackers to intercept plaintext traffic and obtain legitimate credentials or hijack active sessions.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the installed firmware versionAccess the device admin interface or check system information page to view the firmware version. Alternatively, check the device documentation or login banner for version details.Affected if The firmware version displayed is 1.0.4 or falls within the 1.0.x series that lacks HTTPS support.
-
Verify if HTTPS is accessible on the deviceAttempt to access the device using https:// (port 443) in addition to http:// (port 80). Check if the connection succeeds or if TLS handshake occurs.Affected if Only HTTP (port 80) responds and HTTPS (port 443) is unavailable or fails to connect, indicating TLS is not implemented.
-
Inspect the web interface for security indicatorsOpen the device web interface in a browser and examine the URL bar. Look for lock icon indicating encrypted connection, or lack thereof.Affected if The connection shows as 'Not Secure' or 'Not Private' warning, confirming plaintext HTTP is in use.
-
Assess network exposure of the deviceDetermine if the device is directly accessible on the network rather than isolated. Check firewall rules and network segmentation for the device IP range.Affected if The device is reachable on the local network or broader network segment without VPN, as this enables the network-adjacent attack vector.
You are affected if your Circutor Q-SMT device runs firmware version 1.0.4 (or 1.0.x) with only HTTP access and is network-accessible, allowing plaintext traffic interception.
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 dataContact the vendor for a firmware update that includes HTTPS/TLS support. As a compensating control, isolate the device on a dedicated network segment and restrict access through a VPN or jump host until a patched firmware version is available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8890 — 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-8890 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