Some vulnerabilities have been discovered in KTorrent, which can be exploited by malicious users to compromise a vulnerable system and malicious people to bypass certain security restrictions. 1) The web interface plugin does not properly restrict access to the torrent upload functionality. This can be exploited to upload arbitrary torrent files by sending specially crafted HTTP POST request to the affected application. 2) The web interface plugin does not properly sanitise request parameters before passing them to the PHP interpreter. This can be exploited to inject and execute arbitrary PHP code by passing specially crafted parameters to the PHP scripts of the web interface. Successful exploitation of the vulnerabilities requires that the web interface plugin is enabled (not the default setting). The vulnerabilities are confirmed in version 3.1.3. Prior versions may also be affected. Reproducible: Always Not a very good solution: update to version 3.1.4.
http://secunia.com/advisories/32442/ We have 3.1.4 in the tree, the advisory says only 3.x is vulnerable. Topic and whiteboard should be changed accordingly. Maintainers: Can we remove the vulnerable version 3.1.3? Unfortunately, I don't have edit rights.
Note that the 2.x version of ktorrent is also affected for both issues (file upload, and php command execution). The upload issue can be exploited by unauthorized users to start downloads/seeding for a given torrent. I could not exploit the second issue to execute code when not authorized to the system.
Created attachment 170106 [details] ktorrent-3.1.3-upload.patch Upstream 3.1.4 patch for issue (1).
Created attachment 170108 [details] ktorrent-3.1.3-php-injection.patch Upstream 3.1.4 patch for issue (2).
Created attachment 170109 [details] ktorrent-2.2.7-upload.patch Backported 2.2.7 patch for issue (1).
Created attachment 170111 [details] ktorrent-2.2.7-php-injection.patch Backported 2.2.7 patch for issue (2).
FYI, a 2.2.8 version has been released today to fix this problem.
net-p2p, please bump
ping
Ok now you can CC archies so they stable 2.2.8 asap and remove 2.2.7.
Arches, please test and mark stable: =net-p2p/ktorrent-2.2.8 Target keywords : "amd64 ppc ppc64 sparc x86"
amd64/x86 stable
ppc stable
sparc stable
pp64: *ping*
ppc64 done
Looks like all archies done, so closing. Thanks for cooperation :]
Please don't simply close security bugs. C1, if it proves to be correct, requires a GLSA.
Thank you, Christian. ... and I vote YES.
C1 is correct in my view. This is major severity and needs a GLSA. Request filed.
GLSA 200902-05, sorry for the delay.
