Skip to content
Fencer Vulns
high 7.5

CVE-2024-32758 json

exacqVision - Key exchanges

published 2024-08-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-30545

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

Under certain circumstances the communication between exacqVision Client and exacqVision Server will use insufficient key length and exchange

Patch / fix

  • johnsoncontrols exacqvision_client 24.06
  • johnsoncontrols exacqvision_server 24.06

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-24-214-01 updated cvss 8.3

Johnson Controls exacqVision client and exacqVision server

  • Johnson Controls Inc. exacqVision client Johnson Controls Inc. exacqVision server
    affected: mitigation “Johnson Controls recommends user to update exacqVision Client and exacqVision Server to version 24.06” johnsoncontrols.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 9.0 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA 4.0 9.0 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Johnson Controls exacqVision
  • johnsoncontrols exacqvision_server
  • johnsoncontrols exacqvision_client

Classification

Weakness
  • CWE-326 Inadequate Encryption Strength

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.