Bug 1660406 (CVE-2004-2687)

Summary: CVE-2004-2687 distcc: TCP mode has too permissive default IP address whitelist
Product: [Other] Security Response Reporter: Andrej Nemec <anemec>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: agrover, gwync
Target Milestone: ---Keywords: OtherQA, Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: distcc 3.3.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-10 10:44:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1660407, 1660408    
Bug Blocks:    

Description Andrej Nemec 2018-12-18 09:45:51 UTC
In TCP mode, distcc checks the client IP address against a whitelist, which (iirc) is required but can be set quite loosely. There is of course no guarantee that every user on a permitted client address is friendly.

Once the connection is established the client can reasonably easily manipulate the server into running arbitrary commands.

Upstream issue:

https://github.com/distcc/distcc/issues/155

Comment 1 Andrej Nemec 2018-12-18 09:46:01 UTC
Created distcc tracking bugs for this issue:

Affects: epel-all [bug 1660408]
Affects: fedora-all [bug 1660407]

Comment 2 Joshua Miller 2019-04-10 11:23:11 UTC
IBM will do testing as Red Hat will not have access to the new hardware for testing. Setting to OtherQA.

Comment 3 Product Security DevOps Team 2019-06-10 10:44:08 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.