CVE-2024-48121
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 · uneditedThe HI-SCAN 6040i Hitrax HX-03-19-I was discovered to transmit user credentials in cleartext over the GIOP protocol. This allows attackers to possibly gain access to sensitive information via a man-in-the-middle attack.
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 · high confidenceThe HI-SCAN 6040i Hitrax security scanner transmits user credentials in cleartext over the GIOP protocol, allowing attackers on the network path to intercept authentication credentials via man-in-the-middle attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 HI-SCAN 6040i Hitrax scanner on the networkReview network documentation or scan for the device hostname, MAC OUI (Smiths Detection), or IP address range assigned to security screening equipmentAffected if The HI-SCAN 6040i Hitrax scanner is present in the environment
-
Confirm GIOP protocol is in useCapture network traffic on segments where the scanner communicates with its management server or client workstations. Inspect packet headers or use a protocol analyzer to identify GIOP (General Inter-ORB Protocol) traffic on the typical port 10101 or configured GIOP listener portAffected if GIOP protocol traffic is observed between the scanner and other systems
-
Inspect authentication traffic for encryptionExtract authentication packets from the GIOP traffic capture. Examine the payload for plaintext user credentials, password fields, or authentication tokens sent as cleartext rather than encrypted or hashed valuesAffected if User credentials are transmitted in plaintext within GIOP packets
-
Check GIOP configuration for TLS/encryptionAccess the scanner administration interface or review configuration backups for GIOP settings. Look for transport layer security, TLS, or SSL encryption flags and verify whether they are enabled or disabled for the GIOP communication channelAffected if TLS/encryption is not enabled or is disabled for GIOP communications
If the HI-SCAN 6040i Hitrax scanner uses GIOP protocol without encryption for authentication, credentials are transmitted in cleartext and the environment is affected by this CVE.
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 dataImplement TLS/encryption on GIOP communications, or if the device lacks encrypted protocol support, enforce network segmentation and VPN tunneling to protect credential transmission.
- 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-48121 — 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-48121 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