REDHAT-BUG-2492256: Path Traversal
The GLib D-Bus client-side implementation of the DBUSCOOKIESHA1 SASL authentication mechanism does not validate the cookiecontext parameter received from the server. The D-Bus specification explicitly states that cookie context names must not contain the characters /, \, . (period), spaces, or ASCII control characters. However, GLib's client-side code accepts this value verbatim and uses it to construct a filesystem path via gbuildfilename(). A malicious D-Bus server can supply a cookiecontext containing path traversal sequences such as ../.targetfile, causing the client to read an arbitrary file outside the ~/.dbus-keyrings/ directory. The file contents (specifically the third space-separated token of the first matching line) are then incorporated into a SHA1 hash computation and sent back to the server as part of the authentication response. The server can verify guessed file contents against this SHA1 hash, enabling data exfiltration.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2492256?
The severity of REDHAT-BUG-2492256 is categorized as medium with a score of 4.
What is the main issue described in REDHAT-BUG-2492256?
REDHAT-BUG-2492256 reports a vulnerability in the GLib D-Bus that does not properly validate the cookie_context parameter in the DBUS_COOKIE_SHA1 SASL authentication mechanism.
How does the vulnerability in REDHAT-BUG-2492256 affect the system?
The vulnerability in REDHAT-BUG-2492256 can lead to path traversal attacks due to improper validation of the cookie_context parameter.
How do I fix REDHAT-BUG-2492256?
To fix REDHAT-BUG-2492256, you should update the GLib D-Bus to the latest version that addresses this vulnerability.
What software is affected by REDHAT-BUG-2492256?
The affected software as identified in REDHAT-BUG-2492256 is the GLib D-Bus implementation.