Bug 1035577 (CVE-2013-6404) - CVE-2013-6404 quassel: manipulated clients can access backlog of all users on a shared core
Summary: CVE-2013-6404 quassel: manipulated clients can access backlog of all users on...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2013-6404
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1035578
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 06:55 UTC by Ratul Gupta
Modified: 2019-09-29 13:10 UTC (History)
3 users (show)

Fixed In Version: quassel 0.9.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 02:31:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Ratul Gupta 2013-11-28 06:55:24 UTC
A Quassel core (server daemon) supports being used by multiple users, who all have independent settings, backlog and so on. The backlog is stored in a database shared by all users on a Quassel core, tagged with a user ID. However, some SQL queries didn't check for the correct user ID being provided.

This has the undesired effect that the Quassel core can be tricked into providing the backlog for an IRC channel or query that does not belong to the user session requesting it. Doing this requires a manipulated client sending appropriately crafted requests to the core. This client also needs to be properly authenticated, i.e. to have supplied valid user credentials for one of the users on the core.

References:
http://seclists.org/oss-sec/2013/q4/357

Commit:
https://github.com/quassel/quassel/commit/a1a24da

Comment 1 Ratul Gupta 2013-11-28 06:56:12 UTC
Created quassel tracking bugs for this issue:

Affects: fedora-all [bug 1035578]

Comment 3 Product Security DevOps Team 2019-06-08 02:31:03 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


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