NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
93 matching advisories · page 3 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical10.0 CVE-2022-31161 Roxy-WI is a Web interface for managing HAProxy, Nginx and Keepalived servers. roxy-wi · roxy-wi 2022-07-15 critical10.0 CVE-2022-31137 Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. roxy-wi · roxy-wi 2022-07-08 critical10.0 CVE-2022-31126 Roxy-wi is an open source web interface for managing Haproxy, Nginx, Apache and Keepalived servers. roxy-wi · roxy-wi 2022-07-06 critical10.0 CVE-2022-31125 Roxy-wi is an open source web interface for managing Haproxy, Nginx, Apache and Keepalived servers. roxy-wi · roxy-wi 2022-07-06 high7.5 CVE-2021-4047 The release of OpenShift 4.9.6 included four CVE fixes for the haproxy package, however the patch for CVE-2021-39242 was missing. redhat · openshift 2022-04-11 high7.5 CVE-2022-0711 A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header. haproxy · haproxy, redhat · openshift_container_platform, redhat · software_collections +2 2022-03-02 high7.5 CVE-2021-40346 An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack, allowing an attacker… haproxy · haproxy, debian · debian_linux, fedoraproject · fedora 2021-09-08 high7.5 CVE-2021-39242 An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. haproxy · haproxy, debian · debian_linux, fedoraproject · fedora 2021-08-17 medium5.3 CVE-2021-39241 An issue was discovered in HAProxy 2.0 before 2.0.24, 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. haproxy · haproxy, debian · debian_linux, fedoraproject · fedora 2021-08-17 high7.5 CVE-2021-39240 An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. haproxy · haproxy, debian · debian_linux, fedoraproject · fedora 2021-08-17 critical9.8 CVE-2020-35195 The official haproxy docker images before 1.8.18-alpine (Alpine specific) contain a blank password for a root user. docker · haproxy_docker_image 2020-12-17 high8.8 CVE-2020-11100 In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain l… haproxy · haproxy, debian · debian_linux, redhat · openshift_container_platform +3 2020-04-02 medium5.5 CVE-2013-0163 OpenShift haproxy cartridge: predictable /tmp in set-proxy connection hook which could facilitate DoS redhat · openshift 2019-12-05 critical9.8 CVE-2019-19330 The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demonstrated by carriage return (CR, ASCII 0xd), line feed (LF, ASCII 0xa), and the z… haproxy · haproxy, canonical · ubuntu_linux, debian · debian_linux 2019-11-27 high7.5 CVE-2019-18277 A flaw was found in HAProxy before 2.0.6. haproxy · haproxy 2019-10-23 high7.5 CVE-2019-14243 mastercactapus proxyprotocol vulnerable to denial of service go · github.com/mastercactapus/proxyprotocol 2019-07-23 high7.5 CVE-2019-14241 HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c. haproxy · haproxy 2019-07-23 medium5.9 CVE-2019-11323 HAProxy before 1.9.7 mishandles a reload with rotated keys, which triggers use of uninitialized, and very predictable, HMAC keys. haproxy · haproxy 2019-05-09 high7.5 CVE-2018-20615 An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. haproxy · haproxy, opensuse · leap, canonical · ubuntu_linux +2 2019-03-21 medium6.1 CVE-2019-8953 The HAProxy package before 0.59_16 for pfSense has XSS via the desc (aka Description) or table_actionsaclN parameter, related to haproxy_listeners.php and hapr… netgate · haproxy 2019-02-20 high7.5 CVE-2018-20103 An issue was discovered in dns.c in HAProxy through 1.8.14. haproxy · haproxy, canonical · ubuntu_linux, redhat · openshift_container_platform 2018-12-12 high7.5 CVE-2018-20102 An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HAProxy through 1.8.14. haproxy · haproxy, canonical · ubuntu_linux, redhat · openshift_container_platform 2018-12-12 high7.5 CVE-2018-14645 A flaw was discovered in the HPACK decoder of HAProxy, before 1.8.14, that is used for HTTP/2. haproxy · haproxy, canonical · ubuntu_linux, redhat · openshift +2 2018-09-21 medium5.9 CVE-2018-11469 Incorrect caching of responses to requests including an Authorization header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows attackers to achieve info… haproxy · haproxy, canonical · ubuntu_linux 2018-05-25 high7.5 CVE-2018-10184 An issue was discovered in HAProxy before 1.8.8. haproxy · haproxy, redhat · enterprise_linux 2018-05-09 medium5.3 CVE-2016-2102 HAProxy statistics in openstack-tripleo-image-elements are non-authenticated over the network. haproxy · haproxy 2017-08-22 high7.5 CVE-2016-5360 HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized memory access and crash)… canonical · ubuntu_linux, haproxy · haproxy 2016-06-30 low3.3 CVE-2016-3711 HAproxy in Red Hat OpenShift Enterprise 3.2 and OpenShift Origin allows local users to obtain the internal IP address of a pod by reading the "OPENSHIFT_[names… redhat · openshift, redhat · openshift_origin 2016-06-08 medium5.0 CVE-2015-3281 The buffer_slow_realign function in HAProxy 1.5.x before 1.5.14 and 1.6-dev does not properly realign a buffer that is used for pending outgoing data, which al… debian · debian_linux, haproxy · haproxy, canonical · ubuntu_linux +9 2015-07-06 medium5.0 CVE-2014-6269 Multiple integer overflows in the http_request_forward_body function in proto_http.c in HAProxy 1.5-dev23 before 1.5.4 allow remote attackers to cause a denial… haproxy · haproxy 2014-09-30

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.