Homepage

Find out if you have vulnerabilities that put you at risk

Test your applications
Toggle filtering controls
Report a new vulnerability
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.18-2ubuntu3.10
Has fix
ubuntu:16.04Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.14Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.29-1ubuntu4.6
Has fix
ubuntu:18.04Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.10-10+deb8u14
Has fix
debian:8Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-2ubuntu2
Has fix
ubuntu:20.04Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.8Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-3
Has fix
debian:unstablePublished 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.15Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.6Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.10Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-3
Has fix
debian:12Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-3
Has fix
debian:13Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-2ubuntu2
Has fix
ubuntu:20.10Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-2ubuntu2
Has fix
ubuntu:21.04Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.7-1ubuntu4.22
Has fix
ubuntu:14.04Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.7Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-2ubuntu2
Has fix
ubuntu:19.04Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.38-2ubuntu2
Has fix
ubuntu:19.10Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.11Published 3 Apr 2019
  • L
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions *
No fix available
ubuntu:12.04Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.16Published 3 Apr 2019
  • M
Use of Incorrectly-Resolved Name or ReferenceCVE-2019-0220
Affects apache2 | Versions <2.4.39-r0
Has fix
alpine:3.17Published 3 Apr 2019