BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-25690High confidence

Apache HTTP Server: HTTP request splitting with mod_rewrite and mod_proxy

Apache Software Foundation · Apache HTTP Server

Official source article: Siemens SSA-943925 ↗. Check the applicable product and release in the original source.

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 84.51% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache HTTP Server and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainapache2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.56-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainapache2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.56-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainapache2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.56-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.4.56-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.4.56-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.4.56-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.4.56-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
CVE-2023-25690 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityhttpd: HTTP request splitting with mod_rewrite and mod_proxy
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • httpd22 as a component of Red Hat JBoss Enterprise Application Platform 6
Summary
A vulnerability was found in httpd. This security issue occurs when some mod_proxy configurations on Apache HTTP Server allow an HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically.
2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2023-25690
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3
  • ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3
Summary
Vulnerability in Apache HTTP Server versions 2.4.0 through 2.4.55. It involves HTTP Request Smuggling due to certain mod_proxy configurations combined with RewriteRule or ProxyPassMatch directives. This flaw can lead to bypassing access controls by an authenticated attacker.
Remediation
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
SSA-943925 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC NMS
Summary
Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.
Remediation
Update to V2.0 SP1 or later version
SSA-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
11 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
  • SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
  • SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
Summary
Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.
Remediation
Update to V2.4 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-29605

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.

What

Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.

Why

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific pattern matches some portion of the user-supplied request-target (URL) data and is then re-inserted into the proxied request-target using variable substitution. For example, something like: RewriteEngine on RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1"; [P] ProxyPassReverse /here/ http://example.com:8080/ Request splitting/smuggling could result in bypass of access controls in the proxy server, proxying unintended URLs to existing origin servers, and cache poisoning. Users are recommended to update to at least version 2.4.56 of Apache HTTP Server.

Why

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-444 ↗

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'). The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-444Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1285Adobe Experience Manager: Mehrere Schwachstellen ermöglichen Privilegieneskalation

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Adobe Experience Manager ausnutzen, Ein Angreifer kann diese Schwachstellen ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode auszuführen oder Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-2694Oracle Hyperion: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Hyperion ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-2031Xerox FreeFlow Print Server: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1807Oracle Fusion Middleware: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1809Oracle Enterprise Manager: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1424Xerox FreeFlow Print Server für Solaris: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1021Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-0583Apache HTTP Server: Mehrere Schwachstellen ermöglichen HTTP Response Splitting

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apache HTTP Server ausnutzen, um einen Response Splitting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1591Juniper JUNOS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Privilegien zu erweitern und Sicherheitsmechanismen inklusive zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2023-3129Adobe Experience Manager: Mehrere Schwachstellen ermöglichen Cross-Site Scripting

Ein entfernter Angreifer kann mehrere Schwachstellen in Adobe Experience Manager ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-0657Adobe Experience Manager: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Adobe Experience Manager ausnutzen, um Code auszuführen, seine Privilegien zu erhöhen, einen Cross-Site-Scripting-Angriff durchzuführen oder Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230308Security Bulletin 08 Mar 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 Mar 2023, published on 8 March 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0575Multiples vulnérabilités dans les produits Juniper Networks

d?id=CVE-2023-21843 Référence CVE CVE-2023-21912 https://www.cve.org/CVERecord?id=CVE-2023-21912 Référence CVE CVE-2023-21963 https://www.cve.org/CVERecord?id=CVE-2023-21963 Référence CVE CVE-2023-21980 https://www.cve.org/CVERecord?id=CVE-2023-21980 Référence CVE CVE-2023-22025 https://www.cve.org/CVERecord?id=CVE-2023-22025 Référence CVE CVE-2023-22067 https://www.cve.org/CVERecord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-22652 https://www.cve.org/CVERecord?id=CVE-2023-22652 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-25690 https://www.cve.org/CVERecord?id=CVE-2023-25690 Référence CVE CVE-2023-2700 https://www.cve.org/CVERecord?id=CVE-2023-2700 Référence CVE CVE-2023-27522 https://www.cve.org/CVERecord?id=CVE-2023-27522 Référence CVE CVE-2023-2828 https://www.cve.org/CVERecord?id=CVE-2023-2828 Référence CVE CVE-2023-30630 https://www.cve.org/CVERecord?id=CVE-2023-30630 Référence CVE CVE-2023-3090 https://www.cve.org/CVERecord?id=CVE-2023-3090 Référence CVE CVE-2023-32067 https://www.cve.org/CVERecord?id=CVE-2023-32067 Référence CVE CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 Référence CVE CVE-2023-32435 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0119Multiples vulnérabilités dans les produits Siemens

ecord?id=CVE-2023-23934 Référence CVE CVE-2023-23946 https://www.cve.org/CVERecord?id=CVE-2023-23946 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-2454 https://www.cve.org/CVERecord?id=CVE-2023-2454 Référence CVE CVE-2023-2455 https://www.cve.org/CVERecord?id=CVE-2023-2455 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25155 https://www.cve.org/CVERecord?id=CVE-2023-25155 Référence CVE CVE-2023-25193 https://www.cve.org/CVERecord?id=CVE-2023-25193 Référence CVE CVE-2023-25588 https://www.cve.org/CVERecord?id=CVE-2023-25588 Référence CVE CVE-2023-25690 https://www.cve.org/CVERecord?id=CVE-2023-25690 Référence CVE CVE-2023-25727 https://www.cve.org/CVERecord?id=CVE-2023-25727 Référence CVE CVE-2023-26081 https://www.cve.org/CVERecord?id=CVE-2023-26081 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-26965 https://www.cve.org/CVERecord?id=CVE-2023-26965 Référence CVE CVE-2023-27522 https://www.cve.org/CVERecord?id=CVE-2023-27522 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0705Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2023-1436 Référence CVE CVE-2023-21930 https://www.cve.org/CVERecord?id=CVE-2023-21930 Référence CVE CVE-2023-21937 https://www.cve.org/CVERecord?id=CVE-2023-21937 Référence CVE CVE-2023-21938 https://www.cve.org/CVERecord?id=CVE-2023-21938 Référence CVE CVE-2023-21939 https://www.cve.org/CVERecord?id=CVE-2023-21939 Référence CVE CVE-2023-21968 https://www.cve.org/CVERecord?id=CVE-2023-21968 Référence CVE CVE-2023-22874 https://www.cve.org/CVERecord?id=CVE-2023-22874 Référence CVE CVE-2023-24966 https://www.cve.org/CVERecord?id=CVE-2023-24966 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-25690 https://www.cve.org/CVERecord?id=CVE-2023-25690 Référence CVE CVE-2023-2597 https://www.cve.org/CVERecord?id=CVE-2023-2597 Référence CVE CVE-2023-26048 https://www.cve.org/CVERecord?id=CVE-2023-26048 Référence CVE CVE-2023-26049 https://www.cve.org/CVERecord?id=CVE-2023-26049 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CVE-2023-26136 Référence CVE CVE-2023-26920 https://www.cve.org/CVERecord?id=CVE-2023-26920 Référence CVE CVE-2023-27554 https://www.cve.org/CVERecord?id=CVE-2023-27554 Référence CVE CVE-2023-29261 https://www.cve.org/CVERecord?id=CVE-2023-29261 Référence CVE CVE-2023-32338 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0490Multiples vulnérabilités dans NetApp ONTAP

De multiples vulnérabilités ont été découvertes dans NetApp ONTAP . Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un déni de service à distance et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0418Multiples vulnérabilités dans Zimbra

De multiples vulnérabilités ont été découvertes dans Zimbra. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, un contournement de la politique de sécurité et une injection de code indirecte à distance (XSS).

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0267Multiples vulnérabilités dans Tenable.sc

De multiples vulnérabilités ont été découvertes dans Tenable . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0254Multiples vulnérabilités dans Tenable.sc

De multiples vulnérabilités ont été découvertes dans Tenable.sc . Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0200Multiples vulnérabilités dans Apache HTTP Server

De multiples vulnérabilités ont été découvertes dans Apache HTTP Server . Elles permettent à un attaquant de provoquer un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-001632Apache HTTP Server の mod_proxy 構成における HTTP リクエストスマグリングに関する脆弱性

Apache HTTP Server の mod_proxy 構成には、RewriteRule または ProxyPassMatch が有効になっている場合、HTTP リクエストスマグリングに関する脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0246Kwetsbaarheden verholpen in Adobe Experience Manager

Multiple vulnerabilities affect Apache HTTP Server versions 2.4.0 to 2.4.66, including HTTP request smuggling and splitting via mod_proxy, mod_rewrite, and ProxyPassMatch configurations, alongside critical unauthenticated remote takeover flaws in Oracle products.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
httpd22 as a component of Red Hat JBoss Enterprise Application Platform 6
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles4 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 7 Mar 2023 · Last source change 18 Dec 2025, 15:37 UTC · CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-29605
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    2.4.0 ≤ 2.4.55 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    2.4.0 ≤ 2.4.55 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically.
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch; removed remediation: nvd.nist.gov/CVE-2023-25690.
    Before
    remediation: nvd.nist.gov/CVE-2023-25690
    After
    remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch
    ABB Product Security Incident Response Team (PSIRT) ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2023-29605↗Red Hat Product Security security advisory↗Siemens ProductCERT security advisory · Siemens SSA-943925↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-25690 · cve.blacktree.nl