CVE-2024-32865
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 Server will not properly validate TLS certificates provided by connected devices.
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 Server fails to properly validate TLS certificates from connected devices under certain circumstances, allowing potentially untrusted or malicious devices to establish connections without proper authentication verification.
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.06CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/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 Server versionCheck the installed version of Johnson Controls exacqVision Server via the software itself, its About page, or system inventory toolsAffected if The installed version is any release prior to 24.06 (versions like 24.03, 23.x, 22.x, etc.)
-
Confirm TLS is enabled for device connectionsInspect the exacqVision Server configuration for device connectivity settings and verify whether TLS/SSL encryption is enabled for communications with connected cameras or other devicesAffected if TLS is enabled and the server is accepting connections from IP cameras or other networked devices
-
Check for certificate validation configurationReview the exacqVision Server security or network settings for options related to certificate verification, trust store configuration, or TLS authentication modesAffected if Certificate validation is disabled, set to optional, or uses a custom trust store that may not properly validate device certificates
You are affected if running exacqVision Server versions below 24.06 with TLS-enabled device connections, as the server may accept connections from devices with invalid or untrusted certificates under certain configurations.
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 · scoped24.06
Update to the patched version of exacqVision Server that implements proper TLS certificate chain validation, or ensure connected devices present valid, trusted certificates.
24.06
- 1. Back up the current exacqVision Server configuration and data.
- 2. Download the exacqVision Server version 24.06 or later from the official Johnson Controls download portal.
- 3. Stop the exacqVision Server service.
- 4. Install the updated exacqVision Server package.
- 5. Start the exacqVision Server service.
- 6. Verify that the server is running and connected devices are communicating properly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32865 — 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-32865 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