See how unix compares to other vendors in security performance
Opera before 12.12 on UNIX uses weak permissions for the profile directory, which allows local users to obtain sensitive information by reading a (1) cache file, (2) password file, or (3) configuration file, or (4) possibly gain privileges by modifying or overwriting a configuration file.
Opera before 11.62 on UNIX uses world-readable permissions for temporary files during printing, which allows local users to obtain sensitive information by reading these files.
Opera before 11.62 on UNIX, when used in conjunction with an unspecified printing application, allows local users to overwrite arbitrary files via a symlink attack on a temporary file during printing.
Unspecified vulnerability in the PRC component in Adobe Reader and Acrobat 9.x before 9.4.7 on Windows, Adobe Reader and Acrobat 9.x through 9.4.6 on Mac OS X, Adobe Reader and Acrobat 10.x through 10.1.1 on Windows and Mac OS X, and Adobe Reader 9.x through 9.4.6 on UNIX allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unknown vectors, as exploited in the wild in December 2011.
The Universal 3D (U3D) component in Adobe Reader and Acrobat contains a memory corruption vulnerability which could allow remote attackers to execute code or cause denial-of-service (DoS).
Created attachment 433917 [details] Demonstration client and server
Description of problem:
If a request forwarded by a reverse proxy to the back-end server times out and the proxy is reusing back-end connexions, it may still receive the response and send it to a different client making a later, unrelated request. This can result in the leakage of privileged information.
The code committed to modules/proxy/modproxyhttp.c in rev. 660936 [0] and tagged in 2.2.9 [1] introduced a bug in the case of a proxy time-out such that when a reverse proxy attempts to force a retry, approxyhttpprocessresponse returns OK and so the connection to the back-end server remains intact, allowing the server to send its response. If the connexion is subsequently reused to process another request, the client will receive the response to the earlier request that timed out.
This bug was then introduced into the RHEL5 httpd package by the httpd-2.2.3-proxy229.patch patch (in 2.2.3-16.el5 to judge by the change-log), which rebases modules/proxy to 2.2.9.
The bug was fixed upstream (for Unix and Linux) in rev. 699841 [2], which was tagged in 2.2.10 [3], and (for Windows, Netware and OS2) rev. 953616 [4], which was tagged in 2.2.16 [5].
Enabling "DisableReuse" in ProxyPass directives works around the bug.
0 - http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/modules/proxy/modproxyhttp.c?r1=657443&r2=660936 1 - http://svn.apache.org/viewvc/httpd/httpd/tags/2.2.9/CHANGES?view=markup 2 - http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/modules/proxy/modproxyhttp.c?r1=691230&r2=699841 3 - http://svn.apache.org/viewvc/httpd/httpd/tags/2.2.10/CHANGES?view=markup 4 - http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/modules/proxy/modproxyhttp.c?r1=942878&r2=953616 5 - http://svn.apache.org/viewvc/httpd/httpd/tags/2.2.16/CHANGES?view=markup
Version-Release number of selected component (if applicable):
2.2.3-43.el5
How reproducible:
Send two requests via a reverse proxy, ensuring that the second request times out. A subsequent request via the reverse proxy which reuses the connexion used for the second request will receive the second response.
I have attached a simple Tcl client and server which I have used to reproduce the problem. The client sends a GET request with an ID in the query-string. The server waits a geometrically increasing number of milliseconds before sending a plain-text response comprising the ID. Eventually the proxy times out. In the following request, the client receives the wrong response.
Steps to Reproduce:
1. Configure the web-server to enable keep-alives and set up a reverse proxy with two second time-out:
KeepAlive On
ProxyRequests Off
<Proxy http://localhost:12345/proxytest> Order deny,allow Allow from all </Proxy>
ProxyPass /proxytest http://localhost:12345/proxytest timeout=2 ProxyPassReverse /proxytest http://localhost:12345/proxytest
2. Start the web-server in debug mode to ensure that only one process is running and hence that there is only one connexion to the back-end server available:
sudo /usr/sbin/httpd -X
3. Start the server:
./proxyserver.tcl /proxytest 12345
4. Start the client:
./proxyclient.tcl /proxytest localhost 80
Actual results:
The server outputs the following:
$ ./proxyserver.tcl /proxytest 12345 [2010-07-23 11:07:21.116] [1189] acceptconn: /proxytest sock6 192.168.122.195 58385 [2010-07-23 11:07:21.118] [1189] readreq(sock6,192.168.122.195,58385): GET /proxytest?id=04a700000001 HTTP/1.1 [2010-07-23 11:07:21.119] [1189] readreq(sock6,192.168.122.195,58385): reqid = 04a700000001 [2010-07-23 11:07:21.119] [1189] readreq(sock6,192.168.122.195,58385): Host: centos5:12345 [2010-07-23 11:07:21.119] [1189] readreq(sock6,192.168.122.195,58385): Port: 80 [2010-07-23 11:07:21.119] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-For: 127.0.0.1 [2010-07-23 11:07:21.120] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Host: localhost [2010-07-23 11:07:21.120] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Server: 192.168.122.195 [2010-07-23 11:07:21.120] [1189] readreq(sock6,192.168.122.195,58385): Connection: Keep-Alive [2010-07-23 11:07:21.120] [1189] readreq(sock6,192.168.122.195,58385): request complete, delay = 500. [2010-07-23 11:07:21.622] [1189] writeresp(sock6,192.168.122.195,58385): sending 04a700000001 [2010-07-23 11:07:21.628] [1189] readreq(sock6,192.168.122.195,58385): GET /proxytest?id=04a700000002 HTTP/1.1 [2010-07-23 11:07:21.628] [1189] readreq(sock6,192.168.122.195,58385): reqid = 04a700000002 [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): Host: centos5:12345 [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): Port: 80 [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-For: 127.0.0.1 [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Host: localhost [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Server: 192.168.122.195 [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): Connection: Keep-Alive [2010-07-23 11:07:21.629] [1189] readreq(sock6,192.168.122.195,58385): request complete, delay = 1000. [2010-07-23 11:07:22.631] [1189] writeresp(sock6,192.168.122.195,58385): sending 04a700000002 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): GET /proxytest?id=04a700000003 HTTP/1.1 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): reqid = 04a700000003 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): Host: centos5:12345 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): Port: 80 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-For: 127.0.0.1 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Host: localhost [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Server: 192.168.122.195 [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): Connection: Keep-Alive [2010-07-23 11:07:22.639] [1189] readreq(sock6,192.168.122.195,58385): request complete, delay = 2000. [2010-07-23 11:07:24.641] [1189] writeresp(sock6,192.168.122.195,58385): sending 04a700000003 [2010-07-23 11:07:24.744] [1189] readreq(sock6,192.168.122.195,58385): GET /proxytest?id=04a700000004 HTTP/1.1 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): reqid = 04a700000004 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): Host: centos5:12345 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): Port: 80 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-For: 127.0.0.1 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Host: localhost [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): X-Forwarded-Server: 192.168.122.195 [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): Connection: Keep-Alive [2010-07-23 11:07:24.745] [1189] readreq(sock6,192.168.122.195,58385): request complete, delay = 4000. [2010-07-23 11:07:28.746] [1189] writeresp(sock6,192.168.122.195,58385): sending 04a700000004
The third response is delayed sufficiently to cause the reverse proxy to time out.
The client outputs the following:
$ ./proxyclient.tcl /proxytest localhost 80 [2010-07-23 11:07:21.099] [1191] connect: /proxytest localhost 80 [2010-07-23 11:07:21.114] [1191] writereq(sock5): sending 04a700000001 [2010-07-23 11:07:21.623] [1191] readresp(sock5): header = HTTP/1.1 200 OK [2010-07-23 11:07:21.623] [1191] readresp(sock5): header = Date: Fri, 23 Jul 2010 10:07:21 GMT [2010-07-23 11:07:21.623] [1191] readresp(sock5): header = Last-Modified: Wed, 07 Jul 2010 11:07:21 GMT [2010-07-23 11:07:21.624] [1191] readresp(sock5): header = Content-Length: 14 [2010-07-23 11:07:21.624] [1191] readresp(sock5): header = Content-Type: text/plain; charset=UTF-8 [2010-07-23 11:07:21.624] [1191] readresp(sock5): header = Keep-Alive: timeout=15, max=100 [2010-07-23 11:07:21.624] [1191] readresp(sock5): header = Connection: Keep-Alive [2010-07-23 11:07:21.626] [1191] readresp(sock5): received 04a700000001 [2010-07-23 11:07:21.626] [1191] writereq(sock5): sending 04a700000002 [2010-07-23 11:07:22.631] [1191] readresp(sock5): header = HTTP/1.1 200 OK [2010-07-23 11:07:22.633] [1191] readresp(sock5): header = Date: Fri, 23 Jul 2010 10:07:21 GMT [2010-07-23 11:07:22.633] [1191] readresp(sock5): header = Last-Modified: Wed, 07 Jul 2010 11:07:22 GMT [2010-07-23 11:07:22.634] [1191] readresp(sock5): header = Content-Length: 14 [2010-07-23 11:07:22.634] [1191] readresp(sock5): header = Content-Type: text/plain; charset=UTF-8 [2010-07-23 11:07:22.634] [1191] readresp(sock5): header = Keep-Alive: timeout=15, max=99 [2010-07-23 11:07:22.634] [1191] readresp(sock5): header = Connection: Keep-Alive [2010-07-23 11:07:22.634] [1191] readresp(sock5): received 04a700000002 [2010-07-23 11:07:22.638] [1191] writereq(sock5): sending 04a700000003 [2010-07-23 11:07:24.639] [1191] readresp(sock5): header = HTTP/1.1 502 Bad Gateway [2010-07-23 11:07:24.639] [1191] readresp(sock5): header = Date: Fri, 23 Jul 2010 10:07:22 GMT [2010-07-23 11:07:24.639] [1191] readresp(sock5): header = Keep-Alive: timeout=15, max=98 [2010-07-23 11:07:24.639] [1191] readresp(sock5): header = Connection: Keep-Alive [2010-07-23 11:07:24.639] [1191] readresp(sock5): header = Transfer-Encoding: chunked [2010-07-23 11:07:24.640] [1191] readresp(sock5): header = Content-Type: text/html; charset=iso-8859-1 [2010-07-23 11:07:24.640] [1191] readresp(sock5): header = Expires: Fri, 23 Jul 2010 10:07:22 GMT [2010-07-23 11:07:24.741] [1191] connect: /proxytest localhost 80 [2010-07-23 11:07:24.742] [1191] writereq(sock5): sending 04a700000004 [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = HTTP/1.1 200 OK [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Date: Fri, 23 Jul 2010 10:07:24 GMT [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Last-Modified: Wed, 07 Jul 2010 11:07:24 GMT [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Content-Length: 14 [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Content-Type: text/plain; charset=UTF-8 [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Keep-Alive: timeout=15, max=100 [2010-07-23 11:07:24.743] [1191] readresp(sock5): header = Connection: Keep-Alive [2010-07-23 11:07:24.743] [1191] readresp(sock5): received 04a700000003
On the third request the client receives a 502 response from the reverse proxy. It reconnects, sends the fourth request, but receives the response sent by the back-end server to the previous request.
Expected results:
All requests should receive the same ID in response that they send to the server.
Additional info:
Opera before 10.54 on Windows and Mac OS X, and before 10.60 on UNIX platforms, does not properly restrict access to the full pathname of a file selected for upload, which allows remote attackers to obtain potentially sensitive information via unspecified DOM manipulations.
Cross-site scripting (XSS) vulnerability in Opera before 10.54 on Windows and Mac OS X, and before 10.11 on UNIX platforms, allows remote attackers to inject arbitrary web script or HTML via a data: URI, related to incorrect detection of the "opening site."
Opera before 10.50 on Windows, before 10.52 on Mac OS X, and before 10.60 on UNIX platforms makes widget properties accessible to third-party domains, which allows remote attackers to obtain potentially sensitive information via a crafted web site.
Opera before 10.54 on Windows and Mac OS X, and before 10.60 on UNIX platforms, does not properly restrict certain uses of homograph characters in domain names, which makes it easier for remote attackers to spoof IDN domains via unspecified choices of characters.
Multiple cross-site request forgery (CSRF) vulnerabilities in the web management interface in InterSect Alliance Snare Agent 3.2.3 and earlier on Solaris, Snare Agent 3.1.7 and earlier on Windows, Snare Agent 1.5.0 and earlier on Linux and AIX, Snare Agent 1.4 and earlier on IRIX, Snare Epilog 1.5.3 and earlier on Windows, and Snare Epilog 1.2 and earlier on UNIX allow remote attackers to hijack the authentication of administrators for requests that (1) change the password or (2) change the listening port.
Adobe Reader and Acrobat 9.x before 9.3.3 on UNIX allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
Adobe Reader and Acrobat 9.x before 9.3, and 8.x before 8.2 on Windows and Mac OS X, might allow attackers to cause a denial of service (NULL pointer dereference) via unspecified vectors.
Integer overflow in the U3D implementation in Adobe Reader and Acrobat 9.x before 9.3, and 8.x before 8.2 on Windows and Mac OS X, allows remote attackers to execute arbitrary code via a malformed PDF document.
Multiple stack-based buffer overflows in the NOS Microsystems getPlus Helper ActiveX control before 1.6.2.49 in gp.ocx in the Download Manager in Adobe Reader and Acrobat 9.x before 9.3, and 8.x before 8.2 on Windows and Mac OS X, might allow remote attackers to execute arbitrary code via unspecified initialization parameters.
The 3D implementation in Adobe Reader and Acrobat 9.x before 9.3, and 8.x before 8.2 on Windows and Mac OS X, might allow attackers to execute arbitrary code via unspecified vectors, related to a "DLL-loading vulnerability."
Adobe Security Bulletin for Adobe Reader and Acrobat APSB10-02 fixes following security flaw:
This update mitigates a script injection vulnerability by changing the Enhanced Security default (CVE-2009-3956).
Adobe Acrobat and Reader contains an array boundary issue in Universal 3D (U3D) support that could lead to remote code execution.
Absolute path traversal vulnerability in cvs.php in OCS Inventory NG before 1.02.1 on Unix allows remote attackers to read arbitrary files via a full pathname in the log parameter.
UCM-CQ in IBM Rational ClearCase 7.0.0.x before 7.0.0.5, 7.0.1.x before 7.0.1.4, and 7.1.x before 7.1.0.1 on Linux and AIX places a username and password on the command line, which allows local users to obtain credentials by listing the process.
Heap-based buffer overflow in the cache manager in the client in OpenAFS 1.0 through 1.4.8 and 1.5.0 through 1.5.58 on Unix platforms allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via an RX response containing more data than specified in a request, related to use of XDR arrays.
Adobe Reader was built to use insecure RPATH in the binary.
This issue could possibly be exploited by a local attacker to run arbitrary code as some other user if victim user can be convinced to run Adobe Reader in an attacker controlled directory with specially crafted content.
PatchLink Update client for Unix, as used by Novell ZENworks Patch Management Update Agent for Linux/Unix/Mac (LUM) 6.2094 through 6.4102 and other products, allows local users to (1) truncate arbitrary files via a symlink attack on the /tmp/patchlink.tmp file used by the logtrimmer script, and (2) execute arbitrary code via a symlink attack on the /tmp/plshutdown file used by the rebootTask script.
Multiple unspecified vulnerabilities in IBM Hardware Management Console (HMC) 7 R3.2.0 allow attackers to gain privileges via "some HMC commands."
IBM DB2 UDB 9.1 before Fixpak 4 does not properly handle use of large numbers of file descriptors, which might allow attackers to have an unknown impact involving "memory corruption." NOTE: the vendor description of this issue is too vague to be certain that it is security-related.
IBM DB2 UDB 9.1 before Fixpak 4 uses incorrect permissions on ACLs for DB2NODES.CFG, which has unknown impact and attack vectors. NOTE: the vendor description of this issue is too vague to be certain that it is security-related.
Unspecified vulnerability in (1) DB2WATCH and (2) DB2FREEZE in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors.
Unspecified vulnerability in the DB2DART tool in IBM DB2 UDB 9.1 before Fixpak 4 allows attackers to execute arbitrary commands as the DB2 instance owner, related to invocation of TPUT by DB2DART.
Unspecified vulnerability in DB2LICD in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors, related to creation of an "insecure directory."
IBM DB2 UDB 9.1 before Fixpak 4 assigns incorrect privileges to the (1) DB2ADMNS and (2) DB2USERS alternative groups, which has unknown impact. NOTE: the vendor description of this issue is too vague to be certain that it is security-related.