CVE-2024-32931

Johnsoncontrols Exacqvision Web Service ≤ 24.03

Published

01 August 2024

Modified

09 August 2024

Patch / advisory

View advisory

CVSS Score v3.1 5.7

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS Score 0.0038 31th percentile

Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2024-32931 is a medium-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability in Johnsoncontrols Exacqvision Web Service. Its CVSS base score is 5.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-30701

Vulnerability Data

Under certain circumstances the exacqVision Web Service can expose authentication token details within communications.

CWE(s): CWE-598 NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32864Same product: Johnsoncontrols Exacqvision Web Service

CVE-2024-32863Same product: Johnsoncontrols Exacqvision Web Service

CVE-2024-32862Same product: Johnsoncontrols Exacqvision Web Service

CVE-2025-14808Shared CWE-598

CVE-2025-3637Shared CWE-598

CVE-2024-23766Shared CWE-598

CVE-2025-40742Shared CWE-598

CVE-2023-50954Shared CWE-598

CVE-2025-13219Shared CWE-598

CVE-2025-14811Shared CWE-598

Affected Assets

johnsoncontrols

exacqvision web service

≤ 24.03

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V3.4.5
V14.2.1

Mitigating Controls (NIST 800-53 r5) AI

SC-8 Transmission Confidentiality and Integrity partial match

Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in URLs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.

PR.DS-02 partial match

prevents

HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect sensitive data leakage via query strings.

A.8.12 Data leakage prevention partial match

mitigates

DLP solutions can detect and block sensitive data in URLs.

A.8.20 Networks security partial match

degrades

Network security controls can enforce HTTPS and block sensitive data in URLs.

A.8.26 Application security requirements partial match

prevents

Application security requirements should mandate avoiding sensitive data in query strings.