CVE-2024-32864
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 exacqVision Web Services will not enforce secure web communications (HTTPS)
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 confidenceexacqVision Web Services fails to enforce HTTPS under certain conditions, allowing sensitive data to be transmitted over unencrypted HTTP connections. This could enable man-in-the-middle attacks where attackers intercept or modify data in transit.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 installed exacqVision versionAccess the exacqVision web interface or check the application About/Help section to locate the software version numberAffected if The installed version is 24.03 or lower (any version <= 24.03)
-
Verify HTTP port accessibilityAttempt to access the web service over HTTP (port 80) using a browser or curl command: http://[server-ip]Affected if The application responds over HTTP without redirecting to HTTPS
-
Check for HTTPS enforcement in configurationExamine the exacqVision web server configuration files or admin panel for settings related to SSL/TLS enforcement and HTTP-to-HTTPS redirect rulesAffected if HTTP-to-HTTPS redirect is not configured or is disabled
-
Inspect response headers for HSTSMake a request to the HTTPS endpoint and inspect the response headers for the Strict-Transport-Security header: curl -I https://[server-ip]Affected if The Strict-Transport-Security header is missing from HTTPS responses
You are affected if the installed exacqVision version is 24.03 or lower AND the service accepts unencrypted HTTP connections without enforcing HTTPS redirects or HSTS.
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 · scopedConfigure the web server or application to enforce HTTPS redirects and implement HSTS (HTTP Strict Transport Security) headers to ensure all communications occur over encrypted channels.
Exacqvision Web Service 24.03.1 or later
- Confirm current Exacqvision Web Service version by accessing the system admin interface or checking the installed software
- Download Exacqvision version 24.03.1 or later from the official Johnson Controls download portal
- Stop the Exacqvision Web Service before applying the update
- Apply the update following standard Exacqvision upgrade procedures
- After upgrade, verify that HTTPS enforcement is working by attempting HTTP access and confirming it redirects to HTTPS
- Verify the web service is accessible only via HTTPS and that insecure HTTP connections are refused
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32864 — 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-32864 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