Created
October 2, 2018 18:23
-
-
Save Cogitri/775048d44eae0f6403366e801cd2a949 to your computer and use it in GitHub Desktop.
vulns
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
exempi is affected by CVE: CVE-2018-12648 SEVERITY: 4.3 | |
flac is affected by CVE: CVE-2017-6888 SEVERITY: 4.3 | |
fontforge is affected by CVE: CVE-2017-17521 SEVERITY: 6.8 | |
gksu is affected by CVE: CVE-2014-2886 SEVERITY: 6.8 | |
hdf5 is affected by CVE: CVE-2017-17505 SEVERITY: 4.3 | |
hdf5 is affected by CVE: CVE-2017-17506 SEVERITY: 4.3 | |
hdf5 is affected by CVE: CVE-2017-17507 SEVERITY: 4.3 | |
hdf5 is affected by CVE: CVE-2017-17508 SEVERITY: 4.3 | |
hdf5 is affected by CVE: CVE-2017-17509 SEVERITY: 6.8 | |
jasper is affected by CVE: CVE-2018-9055 SEVERITY: 4.3 | |
jasper is affected by CVE: CVE-2018-9252 SEVERITY: 4.3 | |
ldns is affected by CVE: CVE-2017-1000231 SEVERITY: 7.5 | |
ldns is affected by CVE: CVE-2017-1000232 SEVERITY: 7.5 | |
libcroco is affected by CVE: CVE-2017-7960 SEVERITY: 4.3 | |
libcroco is affected by CVE: CVE-2017-7961 SEVERITY: 6.8 | |
libcroco is affected by CVE: CVE-2017-8834 SEVERITY: 4.3 | |
libcroco is affected by CVE: CVE-2017-8871 SEVERITY: 7.1 | |
libexif is affected by CVE: CVE-2017-7544 SEVERITY: 6.4 | |
libgxps is affected by CVE: CVE-2017-11590 SEVERITY: 4.3 | |
libid3tag is affected by CVE: CVE-2004-2779 SEVERITY: 5.0 | |
libid3tag is affected by CVE: CVE-2017-11550 SEVERITY: 4.3 | |
libid3tag is affected by CVE: CVE-2017-11551 SEVERITY: 4.3 | |
libimobiledevice is affected by CVE: CVE-2016-5104 SEVERITY: 5.0 | |
liblouis is affected by CVE: CVE-2018-12085 SEVERITY: 6.8 | |
libpgf is affected by CVE: CVE-2015-6673 SEVERITY: 7.5 | |
libsass is affected by CVE: CVE-2018-11499 SEVERITY: 7.5 | |
libsass is affected by CVE: CVE-2018-11693 SEVERITY: 5.8 | |
libsass is affected by CVE: CVE-2018-11694 SEVERITY: 6.8 | |
libsass is affected by CVE: CVE-2018-11696 SEVERITY: 6.8 | |
libsass is affected by CVE: CVE-2018-11697 SEVERITY: 5.8 | |
libsass is affected by CVE: CVE-2018-11698 SEVERITY: 5.8 | |
libsndfile is affected by CVE: CVE-2017-12562 SEVERITY: 7.5 | |
libsndfile is affected by CVE: CVE-2017-14245 SEVERITY: 5.8 | |
libsndfile is affected by CVE: CVE-2017-14246 SEVERITY: 5.8 | |
libsndfile is affected by CVE: CVE-2017-14634 SEVERITY: 4.3 | |
libsndfile is affected by CVE: CVE-2017-6892 SEVERITY: 6.8 | |
libsndfile is affected by CVE: CVE-2017-8361 SEVERITY: 4.3 | |
libsndfile is affected by CVE: CVE-2017-8362 SEVERITY: 4.3 | |
libsndfile is affected by CVE: CVE-2017-8363 SEVERITY: 4.3 | |
libsndfile is affected by CVE: CVE-2017-8365 SEVERITY: 4.3 | |
libsndfile is affected by CVE: CVE-2018-13139 SEVERITY: 6.8 | |
libsndfile is affected by CVE: CVE-2018-13419 SEVERITY: 5.0 | |
libtar is affected by CVE: CVE-2013-4420 SEVERITY: 5.8 | |
libusbmuxd is affected by CVE: CVE-2016-5104 SEVERITY: 5.0 | |
libvncserver is affected by CVE: CVE-2018-7225 SEVERITY: 7.5 | |
libvorbis is affected by CVE: CVE-2018-10392 SEVERITY: 6.8 | |
libvorbis is affected by CVE: CVE-2018-10393 SEVERITY: 5.0 | |
linux4.1 is affected by CVE: CVE-2015-8767 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2016-2053 SEVERITY: 4.7 | |
linux4.1 is affected by CVE: CVE-2017-1000405 SEVERITY: 6.9 | |
linux4.1 is affected by CVE: CVE-2017-1000407 SEVERITY: 6.1 | |
linux4.1 is affected by CVE: CVE-2017-1000410 SEVERITY: 5.0 | |
linux4.1 is affected by CVE: CVE-2017-12193 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-15102 SEVERITY: 6.9 | |
linux4.1 is affected by CVE: CVE-2017-15115 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-15116 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-15127 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-15129 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-16912 SEVERITY: 7.1 | |
linux4.1 is affected by CVE: CVE-2017-16913 SEVERITY: 7.1 | |
linux4.1 is affected by CVE: CVE-2017-16914 SEVERITY: 7.1 | |
linux4.1 is affected by CVE: CVE-2017-16939 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-16994 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2017-17052 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-17053 SEVERITY: 7.6 | |
linux4.1 is affected by CVE: CVE-2017-17805 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-17806 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-17807 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2017-18075 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-18079 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-18174 SEVERITY: 7.5 | |
linux4.1 is affected by CVE: CVE-2017-18193 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18202 SEVERITY: 6.9 | |
linux4.1 is affected by CVE: CVE-2017-18203 SEVERITY: 1.9 | |
linux4.1 is affected by CVE: CVE-2017-18204 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2017-18208 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18216 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2017-18218 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-18221 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18222 SEVERITY: 4.6 | |
linux4.1 is affected by CVE: CVE-2017-18224 SEVERITY: 1.9 | |
linux4.1 is affected by CVE: CVE-2017-18241 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18249 SEVERITY: 4.4 | |
linux4.1 is affected by CVE: CVE-2017-18255 SEVERITY: 4.6 | |
linux4.1 is affected by CVE: CVE-2017-18257 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18261 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2017-18270 SEVERITY: 3.6 | |
linux4.1 is affected by CVE: CVE-2017-2618 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-1000204 SEVERITY: 6.3 | |
linux4.1 is affected by CVE: CVE-2018-10021 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-10074 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-10087 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2018-10124 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2018-10675 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2018-1068 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2018-10878 SEVERITY: 6.1 | |
linux4.1 is affected by CVE: CVE-2018-10879 SEVERITY: 6.1 | |
linux4.1 is affected by CVE: CVE-2018-10880 SEVERITY: 7.1 | |
linux4.1 is affected by CVE: CVE-2018-10881 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-10940 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-1120 SEVERITY: 3.5 | |
linux4.1 is affected by CVE: CVE-2018-11232 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-1130 SEVERITY: 4.9 | |
linux4.1 is affected by CVE: CVE-2018-11508 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2018-12904 SEVERITY: 4.4 | |
linux4.1 is affected by CVE: CVE-2018-13406 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2018-6927 SEVERITY: 4.6 | |
linux4.1 is affected by CVE: CVE-2018-7480 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2018-8781 SEVERITY: 7.2 | |
linux4.1 is affected by CVE: CVE-2017-18202 SEVERITY: 6.9 | |
linux4.1 is affected by CVE: CVE-2017-18216 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2017-18344 SEVERITY: 2.1 | |
linux4.1 is affected by CVE: CVE-2018-10675 SEVERITY: 7.2 | |
lrzip is affected by CVE: CVE-2017-8842 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-8843 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-8844 SEVERITY: 6.8 | |
lrzip is affected by CVE: CVE-2017-8845 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-8846 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-8847 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-9928 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2017-9929 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2018-11496 SEVERITY: 4.3 | |
lrzip is affected by CVE: CVE-2018-5747 SEVERITY: 4.3 | |
myrepos is affected by CVE: CVE-2018-7032 SEVERITY: 5.1 | |
nodejs is affected by CVE: CVE-2018-7160 SEVERITY: 6.8 | |
nodejs is affected by CVE: CVE-2018-7161 SEVERITY: 7.8 | |
nodejs is affected by CVE: CVE-2018-7162 SEVERITY: 7.8 | |
nodejs is affected by CVE: CVE-2018-7164 SEVERITY: 5.0 | |
openexr is affected by CVE: CVE-2017-12596 SEVERITY: 6.8 | |
openexr is affected by CVE: CVE-2017-14988 SEVERITY: 4.3 | |
openexr is affected by CVE: CVE-2017-9110 SEVERITY: 4.3 | |
openexr is affected by CVE: CVE-2017-9111 SEVERITY: 6.8 | |
openexr is affected by CVE: CVE-2017-9112 SEVERITY: 4.3 | |
openexr is affected by CVE: CVE-2017-9113 SEVERITY: 4.3 | |
openexr is affected by CVE: CVE-2017-9114 SEVERITY: 4.3 | |
openexr is affected by CVE: CVE-2017-9115 SEVERITY: 6.8 | |
openexr is affected by CVE: CVE-2017-9116 SEVERITY: 4.3 | |
opentmpfiles is affected by CVE: CVE-2017-18188 SEVERITY: 2.1 | |
procmail is affected by CVE: CVE-2014-3618 SEVERITY: 7.5 | |
procmail is affected by CVE: CVE-2017-16844 SEVERITY: 10.0 | |
python-Jinja2 is affected by CVE: CVE-2014-1402 SEVERITY: 4.4 | |
python-dbus is affected by CVE: CVE-2011-2533 SEVERITY: 3.3 | |
python-gnupg is affected by CVE: CVE-2013-4242 SEVERITY: 1.9 | |
python-gnupg is affected by CVE: CVE-2018-12020 SEVERITY: 5.0 | |
rsync is affected by CVE: CVE-2017-16548 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2017-16663 SEVERITY: 4.3 | |
sam2p is affected by CVE: CVE-2018-11489 SEVERITY: 6.8 | |
sam2p is affected by CVE: CVE-2018-11490 SEVERITY: 6.8 | |
sam2p is affected by CVE: CVE-2018-12578 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2018-12601 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2018-7487 SEVERITY: 6.8 | |
sam2p is affected by CVE: CVE-2018-7551 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2018-7552 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2018-7553 SEVERITY: 7.5 | |
sam2p is affected by CVE: CVE-2018-7554 SEVERITY: 7.5 | |
squid is affected by CVE: CVE-2018-1000024 SEVERITY: 5.0 | |
squid is affected by CVE: CVE-2018-1000027 SEVERITY: 5.0 | |
squid is affected by CVE: CVE-2018-1172 SEVERITY: 4.3 | |
t1lib is affected by CVE: CVE-2010-2642 SEVERITY: 7.6 | |
t1lib is affected by CVE: CVE-2011-0764 SEVERITY: 6.8 | |
t1lib is affected by CVE: CVE-2011-1552 SEVERITY: 4.3 | |
t1lib is affected by CVE: CVE-2011-1553 SEVERITY: 4.3 | |
t1lib is affected by CVE: CVE-2011-1554 SEVERITY: 4.3 | |
taglib is affected by CVE: CVE-2017-12678 SEVERITY: 6.8 | |
taglib is affected by CVE: CVE-2018-11439 SEVERITY: 4.3 | |
upx is affected by CVE: CVE-2018-11243 SEVERITY: 6.8 | |
vorbis-tools is affected by CVE: CVE-2014-9638 SEVERITY: 5.0 | |
vorbis-tools is affected by CVE: CVE-2014-9639 SEVERITY: 5.0 | |
vorbis-tools is affected by CVE: CVE-2014-9640 SEVERITY: 5.0 | |
vorbis-tools is affected by CVE: CVE-2015-6749 SEVERITY: 4.3 | |
vorbis-tools is affected by CVE: CVE-2017-11331 SEVERITY: 4.3 | |
wavpack is affected by CVE: CVE-2018-10536 SEVERITY: 6.8 | |
wavpack is affected by CVE: CVE-2018-10537 SEVERITY: 6.8 | |
wavpack is affected by CVE: CVE-2018-10538 SEVERITY: 4.3 | |
wavpack is affected by CVE: CVE-2018-10539 SEVERITY: 4.3 | |
wavpack is affected by CVE: CVE-2018-10540 SEVERITY: 4.3 | |
wavpack is affected by CVE: CVE-2018-6767 SEVERITY: 6.8 | |
wavpack is affected by CVE: CVE-2018-7253 SEVERITY: 6.8 | |
wavpack is affected by CVE: CVE-2018-7254 SEVERITY: 6.8 | |
yaml-cpp is affected by CVE: CVE-2017-11692 SEVERITY: 5.0 | |
yaml-cpp is affected by CVE: CVE-2017-5950 SEVERITY: 4.3 | |
tinyxml2 is affected by CVE: CVE-2018-11210 SEVERITY: 7.5 | |
a2ps is affected by CVE: CVE-2001-1593 SEVERITY: 2.1 | |
a2ps is affected by CVE: CVE-2014-0466 SEVERITY: 6.8 | |
a2ps is affected by CVE: CVE-2015-8107 SEVERITY: 6.8 | |
arpwatch is affected by CVE: CVE-2012-2653 SEVERITY: 10.0 | |
aubio is affected by CVE: CVE-2017-17054 SEVERITY: 4.3 | |
aubio is affected by CVE: CVE-2017-17554 SEVERITY: 4.3 | |
aubio is affected by CVE: CVE-2017-17555 SEVERITY: 4.3 | |
aubio is affected by CVE: CVE-2018-14521 SEVERITY: 6.8 | |
aubio is affected by CVE: CVE-2018-14522 SEVERITY: 6.8 | |
aubio is affected by CVE: CVE-2018-14523 SEVERITY: 6.8 | |
beanstalkd is affected by CVE: CVE-2010-2060 SEVERITY: 7.5 | |
binutils is affected by CVE: CVE-2017-16826 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16827 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16828 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16829 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16830 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16831 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-16832 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-17080 SEVERITY: 4.3 | |
binutils is affected by CVE: CVE-2017-17121 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-17122 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-17123 SEVERITY: 4.3 | |
binutils is affected by CVE: CVE-2017-17124 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-17125 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2017-17126 SEVERITY: 6.8 | |
binutils is affected by CVE: CVE-2018-6323 SEVERITY: 6.8 | |
blktrace is affected by CVE: CVE-2018-10689 SEVERITY: 4.3 | |
catdoc is affected by CVE: CVE-2017-11110 SEVERITY: 6.8 | |
catimg is affected by CVE: CVE-2018-13794 SEVERITY: 7.5 | |
chicken is affected by CVE: CVE-2017-11343 SEVERITY: 5.0 | |
chicken is affected by CVE: CVE-2017-6949 SEVERITY: 6.8 | |
couchdb is affected by CVE: CVE-2018-8007 SEVERITY: 9.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment