Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-4295 Overview
CVE-2025-4295 is an improper certificate validation vulnerability in HotelRunner B2B that enables HTTP Response Splitting attacks. The flaw stems from failure to validate the host component of a TLS certificate, classified under [CWE-297]. Attackers positioned on the network can inject crafted HTTP response data into traffic flowing to or from the HotelRunner B2B platform. Successful exploitation requires low privileges and user interaction. The vulnerability affects HotelRunner B2B versions released before 04.06.2025.
Critical Impact
Network attackers with low privileges can manipulate HTTP responses, enabling cache poisoning, cross-site scripting, and session fixation against HotelRunner B2B users.
Affected Products
- HotelRunner B2B platform versions released before 04.06.2025
- Client systems communicating with HotelRunner B2B endpoints
- Integrated reservation and distribution partners relying on HotelRunner B2B APIs
Discovery Timeline
- 2025-07-22 - CVE CVE-2025-4295 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-4295
Vulnerability Analysis
The vulnerability combines two weaknesses that reinforce each other. HotelRunner B2B fails to properly validate that the certificate presented during TLS negotiation matches the expected host. This gap allows an attacker to intercept and relay traffic between legitimate endpoints using a certificate that would normally be rejected.
Once positioned in the communication path, the attacker can inject carriage return and line feed (CRLF) sequences into HTTP response headers. The receiving client parses the injected content as additional response headers or a second response body. This HTTP Response Splitting condition enables cache poisoning, reflected cross-site scripting, and session manipulation against downstream users.
The Turkish national CERT (USOM) and Siber Güvenlik published advisories referencing the issue under notification TR-25-0169.
Root Cause
The root cause is incomplete TLS certificate validation combined with insufficient output sanitization. The application accepts certificates whose Subject Alternative Name or Common Name does not match the requested host. Response data derived from untrusted input is then written into HTTP headers without stripping CR and LF characters.
Attack Vector
Exploitation requires a network-adjacent position between the HotelRunner B2B service and an authenticated user. The attacker presents a mismatched certificate that the client accepts, then injects malicious header content into forwarded responses. User interaction, such as clicking a crafted link or loading a manipulated resource, is required to trigger the payload.
No public proof-of-concept exploit is available. See the USOM Notification TR-25-0169 and Siber Güvenlik Notification TR-25-0169 for additional technical context.
Detection Methods for CVE-2025-4295
Indicators of Compromise
- HTTP response headers containing unexpected CRLF sequences or duplicate Content-Length and Set-Cookie fields.
- TLS handshakes to HotelRunner B2B endpoints presenting certificates with mismatched Subject Alternative Names.
- Anomalous cached web content served to multiple users from HotelRunner B2B hostnames.
Detection Strategies
- Inspect proxy and web application firewall logs for %0d%0a, \r\n, or CRLF byte sequences in request parameters that reflect into responses.
- Monitor TLS inspection appliances for certificate validation failures or warnings tied to HotelRunner B2B traffic.
- Correlate authentication anomalies, such as unexpected session cookie values, with recent requests to HotelRunner B2B endpoints.
Monitoring Recommendations
- Enable strict certificate validation logging on egress proxies that reach HotelRunner B2B services.
- Alert on HTTP responses whose header blocks exceed expected length or contain embedded status lines.
- Track user-agent sessions that receive duplicate Set-Cookie headers from the same origin within short intervals.
How to Mitigate CVE-2025-4295
Immediate Actions Required
- Upgrade HotelRunner B2B to the release published on or after 04.06.2025.
- Enforce strict TLS certificate pinning or validation between client applications and HotelRunner B2B endpoints.
- Audit recent sessions for suspicious cookie values, redirects, or injected content served through the platform.
Patch Information
HotelRunner addressed the issue in the B2B release dated 04.06.2025. Operators should confirm their deployment is at or beyond this build. Review the USOM Notification TR-25-0169 for vendor coordination details.
Workarounds
- Route HotelRunner B2B traffic through a reverse proxy that enforces strict hostname-to-certificate matching.
- Strip CR and LF characters from any user-controlled parameters before they reach the application.
- Restrict access to HotelRunner B2B APIs to known client networks until patched.
# Configuration example
# Example nginx rule to drop requests containing CRLF injection attempts
if ($args ~* "(%0d|%0a|\r|\n)") {
return 400;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

