CVE-2024-32931
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 · uneditedUnder certain circumstances the exacqVision Web Service can expose authentication token details within communications.
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 exacqVision Web Service has an information disclosure vulnerability where authentication token details are exposed within communications under certain circumstances. This could allow an attacker to intercept or capture tokens from network traffic or service responses, potentially leading to session hijacking.
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<= 24.03CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Determine exacqVision Web Service versionLocate the installed exacqVision Web Service version through the software's about page, service information, or version logging. Common methods include checking the application UI, using system inventory tools, or querying the service directly via its management interface.Affected if The installed version is 24.03 or earlier (any version <= 24.03 is within the affected range)
-
Verify if web service uses unencrypted HTTPCheck the exacqVision Web Service configuration or startup parameters to determine whether it is listening on plain HTTP (typically port 80) rather than HTTPS (typically port 443) or whether TLS/SSL encryption is disabled in the service configuration files.Affected if The service is configured to accept unencrypted HTTP connections (TLS is not enabled)
-
Capture and inspect outbound service responsesUse a network packet capture tool (such as Wireshark or tcpdump) to intercept responses from the exacqVision Web Service, or inspect API responses returned to authenticated clients. Look for authentication tokens, session IDs, or session cookies appearing in the response body, headers, or URL parameters.Affected if Authentication tokens or session identifiers are visible in plaintext within service responses or network traffic
-
Review service configuration for token handlingExamine the exacqVision Web Service configuration files and settings related to authentication, session management, and secure communication. Check whether tokens are being returned in error messages, API responses, or debug output.Affected if Configuration allows tokens to be returned in service responses or exposes them in non-secure contexts
You are affected if the exacqVision Web Service version is 24.03 or earlier AND authentication tokens are transmitted in plaintext or returned in service responses (typically when TLS is not enforced).
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.
dbcve · scopedThe vendor should implement secure token handling practices, including using secure communication channels (TLS), avoiding token exposure in URLs or logs, and ensuring tokens are not returned in service responses or error messages.
Exacqvision 24.06 or later
- Identify the Exacqvision Web Service version currently installed
- Backup current configuration and data
- Download Exacqvision version 24.06 or later from the Johnson Controls downloads portal
- Stop the Exacqvision Web Service
- Install the updated version
- Restart the Exacqvision Web Service
- Verify that authentication tokens are no longer exposed in communications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32931 — 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-32931 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