Bug 1257875 - tor: Logging malformed hostnames in socks5 requests leaks sensitive information
tor: Logging malformed hostnames in socks5 requests leaks sensitive information
Status: CLOSED CURRENTRELEASE
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20150825,reported=2...
: Security
Depends On: 1257877 1257878
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-28 06:02 EDT by Adam Mariš
Modified: 2016-01-10 13:06 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-10 13:06:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2015-08-28 06:02:30 EDT
A bug was found in src/or/buffers.c::parse_socks(), where escaped() function on the request address is used rather than escaped_safe_str_client(). When a socks5 client application sends a request with a malformed hostname, the full hostaname is logged, while rejecting the connection, instead of logging [scrubbed] name, respecting the SafeLogging configuration.

Upstream patch:

https://gitweb.torproject.org/tor.git/commit/?id=19df037e53331ae528b876f225be08f198e0f8b6
Comment 1 Adam Mariš 2015-08-28 06:03:23 EDT
Created tor tracking bugs for this issue:

Affects: fedora-all [bug 1257877]
Affects: epel-all [bug 1257878]

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