Manager Proxy vulnerabilitiesAnd the versions its exploited flaws hit.
Manager Proxy is made by Suse. We track 18 published vulnerabilities in it, across 4 versions. 4 of them are on the list of flaws known to be exploited, the newest added on 12 May 2023. If you run Manager Proxy, check your version against the exploited flaws below and patch those first.
The most recent Manager Proxy flaw added to the known-exploited list is CVE-2016-3427, on 12 May 2023. We keep watching the known-exploited list.
Which versions of Manager Proxy do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2016-3427Exploited list, 12 May 2023
Oracle Java SE and JRockit Unspecified Vulnerability
2.1 - CVE-2021-4034Exploited list, 27 Jun 2022
Red Hat Polkit Out-of-Bounds Read and Write Vulnerability
4.1 - CVE-2016-3715Exploited list, 3 Nov 2021
ImageMagick Arbitrary File Deletion Vulnerability
2.1 - CVE-2016-3718Exploited list, 3 Nov 2021
ImageMagick Server-Side Request Forgery (SSRF) Vulnerability
2.1
Which Manager Proxy vulnerabilities are being exploited?
4 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Oracle Java SE and JRockit Unspecified Vulnerability
Oracle Java SE and JRockit contains an unspecified vulnerability that allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Java Management Extensions (JMX).
- 7.8Red Hat Polkit Out-of-Bounds Read and Write Vulnerability
The Red Hat polkit pkexec utility contains an out-of-bounds read and write vulnerability that allows for privilege escalation with administrative rights.
- 5.5ImageMagick Arbitrary File Deletion Vulnerability
ImageMagick contains an unspecified vulnerability that could allow users to delete files by using ImageMagick's 'ephemeral' pseudo protocol, which deletes files after reading.
- 5.5ImageMagick Server-Side Request Forgery (SSRF) Vulnerability
ImageMagick contains an unspecified vulnerability that allows attackers to perform server-side request forgery (SSRF) via a crafted image.
Which Manager Proxy flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 95%
A local privilege escalation vulnerability was found on polkit's pkexec utility.
- 76%
The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted image.
- 75%
The EPHEMERAL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to delete arbitrary files via a crafted image.
- 62%CVE-2016-1286High
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to...
- 59%CVE-2016-1285Medium
named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 does not properly handle DNAME records when parsing fetch reply messages, which allows remote attackers to cause a denial of service (assertion...
- 45%CVE-2016-4957High
ntpd in NTP before 4.2.8p8 allows remote attackers to cause a denial of service (daemon crash) via a crypto-NAK packet.
- 17%CVE-2016-4953High
ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (ephemeral-association demobilization) by sending a spoofed crypto-NAK packet with incorrect authentication data at a certain time.
- 16%CVE-2016-4956Medium
ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (interleaved-mode transition and time change) via a spoofed broadcast packet.
- 13%CVE-2016-4954High
The process_packet function in ntp_proto.c in ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (peer-variable modification) by sending spoofed packets from many source IP addresses...
Running Manager Proxy? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Oracle Java SE and JRockit contains an unspecified vulnerability that allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Java Management Extensions (JMX). This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It can also be exploited by supplying data to APIs in the specified component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service.
- Matched to
- Manager Proxy on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 18 published vulnerabilities listed under the name Manager Proxy, across 4 versions. The most recent Manager Proxy flaw added to the known-exploited list is CVE-2016-3427, on 12 May 2023.
4 are on the list of flaws known to be exploited. The most recently added are CVE-2016-3427, CVE-2021-4034 and CVE-2016-3715.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-3427, affects 2.1. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Manager Proxy. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.