Linux Security
Linux Security
Linux Security

Debian: DSA-2322-1: bugzilla security update

Date 10 Oct 2011
Posted By LinuxSecurity Advisories
Several vulnerabilities were discovered in Bugzilla, a web-based bug tracking system. CVE-2010-4572
Hash: SHA1

- -------------------------------------------------------------------------
Debian Security Advisory DSA-2322-1                   This email address is being protected from spambots. You need JavaScript enabled to view it.                        Jonathan Wiltshire
October 10, 2011             
- -------------------------------------------------------------------------

Package        : bugzilla
Vulnerability  : several
Problem type   : remote
Debian-specific: no
CVE ID         : CVE-201-2979 CVE-2010-4567 CVE-2010-4568 CVE-2010-4572 
                 CVE-2011-0046 CVE-2011-0048 CVE-2011-2379 CVE-2011-2380 
                 CVE-2011-2381 CVE-2011-2978 

Several vulnerabilities were discovered in Bugzilla, a web-based bug
tracking system.


  By inserting particular strings into certain URLs, it was
  possible to inject both headers and content to any

CVE-2010-4567, CVE-2011-0048

  Bugzilla has a "URL" field that can contain several types
  of URL, including "javascript:" and "data:" URLs. However,
  it does not make "javascript:" and "data:" URLs into
  clickable links, to protect against cross-site scripting
  attacks or other attacks. It was possible to bypass this
  protection by adding spaces into the URL in places that
  Bugzilla did not expect them. Also, "javascript:" and
  "data:" links were *always* shown as clickable to
  logged-out users.


  It was possible for a user to gain unauthorized access to
  any Bugzilla account in a very short amount of time (short
  enough that the attack is highly effective).


  Various pages were vulnerable to Cross-Site Request
  Forgery attacks. Most of these issues are not as serious
  as previous CSRF vulnerabilities.


  When a user changes his email address, Bugzilla trusts
  a user-modifiable field for obtaining the current e-mail
  address to send a confirmation message to. If an attacker
  has access to the session of another user (for example,
  if that user left their browser window open in a public
  place), the attacker could alter this field to cause
  the email-change notification to go to their own address.
  This means that the user would not be notified that his
  account had its email address changed by the attacker.


  For flagmails only, attachment descriptions with a newline
  in them could lead to the injection of crafted headers in
  email notifications when an attachment flag is edited.


  Bugzilla uses an alternate host for attachments when
  viewing them in raw format to prevent cross-site scripting
  attacks. This alternate host is now also used when viewing
  patches in "Raw Unified" mode because Internet Explorer 8
  and older, and Safari before 5.0.6 do content sniffing,
  which could lead to the execution of malicious code.

CVE-2011-2380 CVE-201-2979

  Normally, a group name is confidential and is only visible
  to members of the group, and to non-members if the group
  is used in bugs. By crafting the URL when creating or
  editing a bug, it was possible to guess if a group existed
  or not, even for groups which weren't used in bugs and so
  which were supposed to remain confidential.

For the oldstable distribution (lenny), it has not been practical to
backport patches to fix these bugs. Users of bugzilla on lenny are 
strongly advised to upgrade to the version in the squeeze distribution.

For the stable distribution (squeeze), these problems have been fixed in

For the testing distribution (wheezy) and the unstable distribution (sid),
the bugzilla packages have been removed.

We recommend that you upgrade your bugzilla packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at:

Mailing list: This email address is being protected from spambots. You need JavaScript enabled to view it.

LinuxSecurity Poll

How frequently do you patch/update your system?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum 0 answer(s) and maximum 3 answer(s).
[{"id":"179","title":"As soon as patches\/updates are released - I track advisories for my distro(s) diligently","votes":"50","type":"x","order":"1","pct":80.65,"resources":[]},{"id":"180","title":"Every so often, when I think of it","votes":"7","type":"x","order":"2","pct":11.29,"resources":[]},{"id":"181","title":"Hardly ever","votes":"5","type":"x","order":"3","pct":8.06,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350

Please vote first in order to view vote results.



bottom 200

Please enable / Bitte aktiviere JavaScript!
Veuillez activer / Por favor activa el Javascript![ ? ]

We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.