Skip to content

Instantly share code, notes, and snippets.

Created February 22, 2014 16:17
Show Gist options
  • Save joernchen/a7c031b6b8df5d5d0b61 to your computer and use it in GitHub Desktop.
Save joernchen/a7c031b6b8df5d5d0b61 to your computer and use it in GitHub Desktop.
Bounty writeup
GitHub RCE by Environment variable injection Bug Bounty writeup
Disclaimer: I'll keep this really short but I hope you'll get the key points.
GitHub blogged a while ago about some internal tool called gerve:
Upon git+sshing to gerve basically looks up your permission
on the repo you want to interact with. Then it bounces you further in
another forced SSH session to the back end where the repo actually is.
At some point I figured that it is possible to inject some environment
variables into gerve/the forked SSH process by setting my username to
something like "joerchen\n\nLD_ASSUME_KERNEL=1\n\n".
LD_ASSUME_KERNEL=1 will prevent the actual command from being run, just
like this:
joernchen ~ $ LD_ASSUME_KERNEL=1 uname -a
uname: error while loading shared libraries: cannot open shared object file: No such file or directory
For the details on this, check man 8
So far so good, how can we use this fact to make SSH execute arbitrary
The technique I came up with used both features of and SSH itself:
How and why did this work?
1.) libfakeroot makes SSH think it's root (we can inject this via
LD_PRELOAD because the ssh binary is not setuid)
2.) ssh tries to read /root/.ssh/known_hosts
3.) ssh fails reading 'cause it's actually running as the git user
4.) ssh connects to $backend and wants to ask the user if
$backend_hostkey is OK.
5.) ssh has no terminal and DISPLAY is set
6.) ssh invokes the command specified in SSH_ASKPASS
From being dropped in /usr/bin/ex we could just say:
and be happy with having a shell as
Copy link

Awesome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment