Secure Global Desktop vulnerabilitiesAnd the versions its exploited flaws hit.
Secure Global Desktop is made by Oracle. We track 33 published vulnerabilities in it, across 11 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 1 December 2021. If you run Secure Global Desktop, check your version against the exploited flaws below and patch those first.
The most recent Secure Global Desktop flaw added to the known-exploited list is CVE-2021-40438, on 1 December 2021. We keep watching the known-exploited list.
Which versions of Secure Global Desktop do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2021-40438Exploited list, 1 Dec 2021
Apache HTTP Server-Side Request Forgery (SSRF)
5.6
Which Secure Global Desktop vulnerabilities are being exploited?
1 flaw is 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.0Apache HTTP Server-Side Request Forgery (SSRF)
A crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user.
Which Secure Global Desktop 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.
- >99%
A crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user.
- 98%CVE-2018-11784Medium
When the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a redirect to a directory (e.g.
- 86%CVE-2014-0226Medium
Race condition in the mod_status module in the Apache HTTP Server before 2.4.10 allows remote attackers to cause a denial of service (heap-based buffer overflow), or possibly obtain sensitive credential information...
- 81%CVE-2019-10092Medium
In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page.
- 75%CVE-2021-33037Medium
Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when...
- 64%CVE-2021-3449Medium
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.
- 57%CVE-2017-7668High
The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows ap_find_token() to search past the end of its input string.
- 57%CVE-2017-9788Critical
In Apache httpd before 2.2.34 and 2.4.x before 2.4.27, the value placeholder in [Proxy-]Authorization headers of type 'Digest' was not initialized or reset before or between successive key=value assignments by...
- 51%CVE-2018-11763Medium
In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect.
Running Secure Global Desktop? 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
A crafted request uri-path can cause mod_proxy to forward the request to an origin server choosen by the remote user. This issue affects Apache HTTP Server 2.4.48 and earlier.
- Matched to
- Secure Global Desktop 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 33 published vulnerabilities listed under the name Secure Global Desktop, across 11 versions. The most recent Secure Global Desktop flaw added to the known-exploited list is CVE-2021-40438, on 1 December 2021.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2021-40438.
Each flaw names its own versions, usually as ranges. The newest, CVE-2021-40438, affects 5.6. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Secure Global Desktop. 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.