CVE-2012-0053

mediumpriority · attend · 56EPSS 0.822 · 100 %ileexploit · functionalEUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
1 exploit · functional
Likely / severe?
82.2% (100th) EPSS
CVSS 4.3 · medium
Is it mine?
36 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · nvd · redhat_csaf

EPSS · scored 2026-10-23

protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during construction of Bad Request (aka 400) error documents, which allows remote attackers to obtain the values of HTTPOnly cookies via vectors involving a (1) long or (2) malformed header in conjunction with crafted web script.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedhttpd-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-0:2.2.17-15.4.ep5.el5.src as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-0:2.2.17-15.4.ep5.el6.src as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-devel-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-devel-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-devel-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-devel-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-manual-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-manual-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-manual-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-manual-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-tools-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedhttpd-tools-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedmod_ssl-1:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedmod_ssl-1:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedmod_ssl-1:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • Fixedmod_ssl-1:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/knowledge/articles/11258

    https://access.redhat.com/errata/RHSA-2012:0542
  • FixedRed Hat JBoss Web Server 1.0redhat_csaf

    The References section of this erratum contains a download link (you must log in to download the update). Before applying the update, back up your existing JBoss Enterprise Web Server installation (including all applications and configuration files). The Apache HTTP Server must be restarted for this update to take effect.

    https://access.redhat.com/errata/RHSA-2012:0543
  • Workaroundhttpd-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-0:2.2.17-15.4.ep5.el5.src as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-0:2.2.17-15.4.ep5.el6.src as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-devel-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-devel-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-devel-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-devel-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-manual-0:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-manual-0:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-manual-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-manual-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-tools-0:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundhttpd-tools-0:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundmod_ssl-1:2.2.17-15.4.ep5.el5.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundmod_ssl-1:2.2.17-15.4.ep5.el5.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 5 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundmod_ssl-1:2.2.17-15.4.ep5.el6.i386 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • Workaroundmod_ssl-1:2.2.17-15.4.ep5.el6.x86_64 as a component of Red Hat JBoss Enterprise Web Server 1 for RHEL 6 Serverredhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

  • WorkaroundRed Hat JBoss Web Server 1.0redhat_csaf

    As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be noted that ErrorDocument setting using path or external URL does not mitigate this issue. It should also be noted that this is not an issue by itself. This can only be exploited via some other cross-site scripting (XSS) flaw found in a web application running on the server and may allow injected JavaScript to gain access to HttpOnly cookies, if the application uses this protection for its cookies.

02

cvss

Technical severity, 0–10. One row per scoring source.

4.3
010

base score 0–10 · higher = more severe · hover a vector to decode

v2.04.3mediumAV:N/AC:M/Au:N/C:P/I:N/A:Nprimary · NVD / NIST USexploitability 8.6 · impact 2.9
v2.04.3mediumAV:N/AC:M/Au:N/C:P/I:N/A:N/E:Hsecondary · CVSS-BT (t0sche)
v2.04.3mediumAV:N/AC:M/Au:N/C:P/I:N/A:Nsecondary · Red Hat Product Security US
03

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-200USLLM-inferred
04

exploits (1)

Public proof-of-concept and weaponised exploit code.

05

affected products (36)

Products and version ranges known to be affected.

showing 20 of 36
06

advisories (2)

Vendor and ecosystem advisories describing this.

  • RHSA-2012:0542Red Hat Security Advisory: httpd security and bug fix update2012-05-07csaf · redhat_csafUS

    Updated httpd packages that fix multiple security issues and one bug are now available for JBoss Enterprise Web Server 1.0.2 for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

  • RHSA-2012:0543Red Hat Security Advisory: httpd security and bug fix update2012-05-07csaf · redhat_csafUS

    An update for the Apache HTTP Server component for JBoss Enterprise Web Server 1.0.2 that fixes multiple security issues and one bug is now available from the Red Hat Customer Portal. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

07

also known as (3)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

published 2012-01-28modified 2026-06-16
09

references (134)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan