It was reported [1] that tinyproxy prior to version 1.8.3, when configured to allow a network range (i.e. "Allow 192.168.0.0/24" versus the default "Allow 127.0.0.1"), would allow any connections from any IP address, turning it into an open proxy. If tinyproxy were configured with one or more Allow statements that use an IP range, this would occur. This has been fixed upstream [2] and affects the versions of tinyproxy as provided by Fedora and EPEL. [1] https://banu.com/bugzilla/show_bug.cgi?id=90 [2] https://banu.com/cgit/tinyproxy/commit/?id=e8426f6662dc467bd1d827100481b95d9a4a23e4
This was assigned the name CVE-2011-1499.
Common Vulnerabilities and Exposures assigned an identifier CVE-2011-1843 to the following vulnerability: Name: CVE-2011-1843 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1843 Assigned: 20110502 Reference: https://banu.com/bugzilla/show_bug.cgi?id=90 Reference: https://banu.com/cgit/tinyproxy/diff/?id=97b9984484299b2ce72f8f4fc3706dab8a3a8439 Integer overflow in conf.c in Tinyproxy before 1.8.3 might allow remote attackers to bypass intended access restrictions in opportunistic circumstances via a TCP connection, related to improper handling of invalid port numbers. The above is a related but slightly different issue (note the same bug, but different commits).
Created tinyproxy tracking bugs for this issue Affects: fedora-all [bug 701687] Affects: epel-all [bug 701688]
tinyproxy-1.8.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
tinyproxy-1.8.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.