Yair is an lightweight command-line-tool to interact with Clair. It is designed for the execution inside a CI Job, for example to determine if an image can be deployed to the production environment.
It can also executed locally without much effort.
Features:
Copy the "config.yaml.tmpl" of this repo and change it to fit your needs.
---
registry:
host: "registry.hub.docker.com"
clair:
host: "localhost:6060"
output:
format: table
rocketchat:
webhook_url: rocket-chat.com/hooks/...
receiver: "#general,@admin"
fail_on:
score: 379
big_vulnerability: true| Config Option | Description |
|---|---|
| registry::host | hostname of the Docker Registry, can be overwritten with "--registry" Argument |
| clair::host | hostname of the Clair Server with Port |
| output::format | specifys the output format, can be "json", "table", "short-table" or "quiet" |
| output::rocketchat | Rocket.Chat ouput, leave config commented if you dont want to use it |
| output::rocketchat::webhook_url | url to the Rocket.Chat hook you configured for this output with http/https prefix |
| output::rocketchat::receiver | comma-separated list of channels to send output to |
| fail_on::score | if the image vulnerability score is above this value, the script will have an returncode of "2" |
| fail_on::big_vulnerability | if set to true and the image has an vulnerability with severity "high" or higher, the script will have an return code of "2" |
Rename the customized "config.yaml.tmpl" to "config.yaml" and move it to the directory you want to execute it in.
The config.yaml will be made accessible to yair with a readonly docker volume:
docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair [namespace/]image[:tag]You can also change the source path to a fixed path where your config.yaml is located.
You can scan public images and private images. If you don't specify a tag, it will assume you want to scan latest.
Supported arguments:
--config Config file location. Defaults to /opt/yair/config/config.yaml
--no-namespace If your image names doesnt contain the "amespace" and its not in the default "library" namespace.
--registry Overwrites the "registry::host" configfile option.
Here are some examples:
docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair myimage
docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair mynamespace/myimage
docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair mynamespace/myimage:mytag
docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair mynamespace/myimage:mytag --registry "my-registry:1234"This is a preview of a scan with output::format "table". Normally images will have many more vulnerabilities, so you will get a bigger table. "Version with fix" will be empty if the vulnerability has not yet been fixed by the distribution.
+---------------------+----------------+------------------------------------------------------------------+--------------------+
| Package | CVE Name | CVE Link | Version with fix |
| Installed Version | Severity | CVE Description | |
+=====================+================+==================================================================+====================+
| wget | RHSA-2017:3075 | https://access.redhat.com/errata/RHSA-2017:3075 | 1.14-15.el7_4.1 |
| | | | |
| 1.14-15.el7 | High | The wget packages provide the GNU Wget file retrieval utility | |
| | | for HTTP, HTTPS, and FTP protocols. Security Fix(es): * A stack- | |
| | | based and a heap-based buffer overflow flaws were found in wget | |
| | | when processing chunked encoded HTTP responses. By tricking an | |
| | | unsuspecting user into connecting to a malicious HTTP server, an | |
| | | attacker could exploit these flaws to potentially execute | |
| | | arbitrary code. (CVE-2017-13089, CVE-2017-13090) Red Hat would | |
| | | like to thank the GNU Wget project for reporting these issues. | |
+---------------------+----------------+------------------------------------------------------------------+--------------------+
scan result for: IMAGE_NAME
the image has "high" vulnerabilitiesThis is a preview of a scan with output::format "short-table". "Version with fix" will be empty if the vulnerability has not yet been fixed by the distribution.
$ docker run -v `pwd`:/opt/yair/config/:ro yfoelling/yair:latest ubuntu
+------------+----------------+------------+--------------------+
| Package | CVE Name | Severity | Version with fix |
|------------+----------------+------------+--------------------|
| systemd | CVE-2017-15908 | Medium | |
| db5.3 | CVE-2017-10140 | Medium | |
| apparmor | CVE-2016-1585 | Medium | |
| glibc | CVE-2017-8804 | Medium | |
| glibc | CVE-2017-12132 | Medium | |
| perl | CVE-2016-1238 | Medium | |
| perl | CVE-2017-12883 | Medium | |
| perl | CVE-2017-12837 | Medium | |
| util-linux | CVE-2016-5011 | Low | |
| util-linux | CVE-2016-2779 | Low | |
| glibc | CVE-2015-8985 | Low | |
| glibc | CVE-2015-5180 | Low | |
| perl | CVE-2017-6512 | Low | |
| shadow | CVE-2013-4235 | Low | |
| shadow | CVE-2017-12424 | Low | |
| pcre3 | CVE-2017-6004 | Low | |
| pcre3 | CVE-2017-7244 | Low | |
| pcre3 | CVE-2017-7186 | Low | |
| coreutils | CVE-2016-2781 | Low | |
| cryptsetup | CVE-2016-4484 | Low | |
| bzip2 | CVE-2016-3189 | Low | |
| ncurses | CVE-2017-13730 | Negligible | |
| ncurses | CVE-2017-13731 | Negligible | |
| ncurses | CVE-2017-13733 | Negligible | |
| ncurses | CVE-2017-13732 | Negligible | |
| ncurses | CVE-2017-10684 | Negligible | |
| ncurses | CVE-2017-13728 | Negligible | |
| ncurses | CVE-2017-11112 | Negligible | |
| ncurses | CVE-2017-11113 | Negligible | |
| ncurses | CVE-2017-13729 | Negligible | |
| ncurses | CVE-2017-13734 | Negligible | |
| ncurses | CVE-2017-10685 | Negligible | |
| glibc | CVE-2016-10228 | Negligible | |
| pcre3 | CVE-2017-7246 | Negligible | |
| pcre3 | CVE-2017-7245 | Negligible | |
| dpkg | CVE-2017-8283 | Negligible | |
+------------+----------------+------------+--------------------+
scan result for: library/ubuntu:latestIf the scan exits with return code 2, then the scanned image has either:
You can configure these thresholds in the config.yaml "fail_on" section.
If a vulnerability is detected and there is already a version of the affected package with a fix, then a number will be added to the score depending on the severity:
| Severity | Score |
|---|---|
| Unknown | 0 |
| Negligible | 1 |
| Low | 16 |
| Medium | 81 |
| High | 265 |
| Critical | 625 |
| Defcon1 | 1296 |
You can run yair localy to any registry.
First install python requirements:
virtualenv --python=python3 pyenv
. pyenv/bin/activate
pip install -r requirements.txtCopy the config template file:
cp config.yaml.tmpl config.yamlNow you can adapt the config to your requirements. You will need to specify a clair host. If you want to start your own clair locally, make sure to wait until all vulnerability-dbs got dowloaded (it takes a few hours)
After you can run yair like this:
# You can change the image to whatever you want to use for testing. I use the nginx public image.
./yair.py nginx --config config.yaml