Bug 751935 – CVE-2011-3656 Mozilla: Possible XSS via HTTP 0.9 errors and content-sniffing

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 751935 - (CVE-2011-3656) CVE-2011-3656 Mozilla: Possible XSS via HTTP 0.9 errors and content-sniffing

Summary:	CVE-2011-3656 Mozilla: Possible XSS via HTTP 0.9 errors and content-sniffing

Status:	CLOSED CURRENTRELEASE

Aliases:	CVE-2011-3656

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20111109,repor...
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2011-11-07 23:40 EST by Huzaifa S. Sidhpurwala
Modified:	2016-03-04 05:54 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-07-29 08:52:32 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Huzaifa S. Sidhpurwala 2011-11-07 23:40:26 EST

Some non-HTTP protocols running on a server might respond to HTTP requests with an error message, and return (parts of) the incoming request. If web browsers content-sniff data returned withouth HTTP headers, an attacker might be able to send data to such a service, and have the server return an error which the browser interprets as HTML/JS. This opens up for XSS.

Reference:
https://bugzilla.mozilla.org/show_bug.cgi?id=667907

Comment 1 Huzaifa S. Sidhpurwala 2011-11-08 04:02:40 EST

Upstream bug says, this is embargoed till 28th Dec 2011. However 3.6.24 likely has the fix, perhaps the bug wont be made public.

Note You need to log in before you can comment on or make changes to this bug.