Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report that a vulnerability exists in the wrong package #408

Closed
usiusi360 opened this issue Mar 31, 2017 · 3 comments
Closed

Report that a vulnerability exists in the wrong package #408

usiusi360 opened this issue Mar 31, 2017 · 3 comments
Labels
Milestone

Comments

@usiusi360
Copy link
Contributor

Environment

Vuls

Hash : vuls v0.3.0 bdf6efe

OS

  • Target Server: CentOS Linux release 7.3.1611 (Core)
  • Vuls Server: CentOS Linux release 7.3.1611 (Core)

Go

  • Go version: go version go1.7.4 linux/amd64

Current Output

image

The content of CVE-ID is a vulnerability related to BIND.
However, the affected package is bash.
And the contents of bind are mixed in changelog.

Addition Details

When two or more packages are the same changelog, the format of the output is changed.

  • Previous output
ChangeLog for: coreutils-8.4-43.el6.x86_64, coreutils-libs-8.4-43.el6.x86_64
* Wed Feb 10 21:00:00 2016 Ondrej Vasik <ovasik@redhat.com> - 8.4-43
- sed should actually be /bin/sed (related #1222140)
* Wed Jan  6 21:00:00 2016 Ondrej Vasik <ovasik@redhat.com> - 8.4-41
- colorls.sh,colorls.csh - call utilities with complete path (#1222140)
- mkdir, mkfifo, mknod - respect default umask/acls when
  COREUTILS_CHILD_DEFAULT_ACLS envvar is set (to match rhel 7 behaviour,
  • Current output
ChangeLog for: 1:openssl-1.0.1e-60.el7_3.1.x86_64,
             : 1:openssl-libs-1.0.1e-60.el7_3.1.x86_64
* Mon Feb  6 21:00:00 2017 Tomáš Mráz <tmraz@redhat.com> 1.0.1e-60.1
- fix CVE-2017-3731 - DoS via truncated packets with RC4-MD5 cipher
- fix CVE-2016-8610 - DoS of single-threaded servers via excessive alerts
@kotakanbe
Copy link
Member

kotakanbe commented Apr 5, 2017

Thanks for reporting.
Do you scan as local scan mode or remote scan mode?

@usiusi360
Copy link
Contributor Author

It occurs only when scanning local scans and docker containers.

@kotakanbe kotakanbe added this to the v0.4.0 milestone Aug 25, 2017
@kotakanbe kotakanbe added the bug label Aug 25, 2017
@kotakanbe
Copy link
Member

This issue has been fixed in v4.0.0.
If you are still in trouble, please reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants