EUVD-2026-34192
GHSA-fqm2-p6px-f54c
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/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
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/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
Lifecycle Timeline
7DescriptionCVE.org
CWE-326 in BOSH allows a local attacker to steal Basic-auth credentials or redirect UAA token requests via MITM. HttpRequestHelper#create_async_endpoint and #send_http_get_request_synchronous hard-code OpenSSL::SSL::VERIFY_NONE, enabling an attacker to intercept traffic between bosh-monitor and the BOSH director or UAA and steal credentials.
Affected versions:
- BOSH: all versions prior to v282.1.9 (inclusive); fixed in v282.1.9 or later
AnalysisAI
Credential theft and UAA token redirection in Cloud Foundry BOSH versions prior to v282.1.9 allows a network-positioned local attacker to intercept Basic-auth secrets and OAuth requests flowing between bosh-monitor and the BOSH director or UAA. The flaw stems from hard-coded OpenSSL::SSL::VERIFY_NONE in the HttpRequestHelper, effectively disabling TLS certificate validation. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Technical ContextAI
BOSH is the Cloud Foundry Foundation's release-engineering and lifecycle-management toolchain used to deploy and operate distributed systems such as Cloud Foundry itself. The bosh-monitor component periodically calls back to the BOSH director and to the User Account and Authentication (UAA) service over HTTPS using a Ruby HttpRequestHelper wrapper around OpenSSL. CWE-326 (Inadequate Encryption Strength) applies because the helper methods create_async_endpoint and send_http_get_request_synchronous pass OpenSSL::SSL::VERIFY_NONE, telling the OpenSSL client to skip server-certificate chain and hostname validation. The result is that TLS provides encryption-in-transit but no authentication of the peer, so any party capable of intercepting the traffic - typically by ARP/DNS poisoning, rogue gateway, or compromise of an adjacent node - can present an arbitrary certificate and complete the handshake. Per CPE cpe:2.3:a:cloud_foundry_foundation:bosh:*, the entire BOSH product line up to v282.1.9 inherits this behavior.
RemediationAI
Vendor-released patch: upgrade BOSH to v282.1.9 or later, which removes the hard-coded OpenSSL::SSL::VERIFY_NONE and enables proper certificate validation in HttpRequestHelper#create_async_endpoint and #send_http_get_request_synchronous; details and version guidance are at https://www.cloudfoundry.org/blog/cve-2026-41860-missing-tls-verify-on-bosh-monitor/. Where immediate upgrade is not possible, restrict the L2/L3 network between bosh-monitor, the BOSH director and UAA to a dedicated management segment so no untrusted host can interpose itself (trade-off: requires network reconfiguration and may break shared-network topologies), enforce static ARP entries or 802.1X on that segment to block ARP/DNS spoofing, and rotate any Basic-auth and UAA client credentials that may have transited the affected path since deployment because they must now be treated as potentially compromised. Disabling bosh-monitor entirely will eliminate the vulnerable call path but at the cost of losing health monitoring and alerting.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
The ssl3_send_client_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this
A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto
Same weakness CWE-326 – Inadequate Encryption Strength
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today