Pepperl+Fuchs WirelessHART-Gateway
Successful exploitation of these vulnerabilities may result in a denial-of-service condition, code execution, and code exposure.
describes (19)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-34565US | critical9.8OT elevated | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.7 to 3.0.9 the SSH and telnet services are active with hard-coded credentials. | ||||
| CVE-2021-34564US | medium5.5 | — | ||
Any cookie-stealing vulnerabilities within the application or browser would enable an attacker to steal the user's credentials to the PEPPERL+FUCHS WirelessHART-Gateway 3.0.9. | ||||
| CVE-2021-34563US | low3.3 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.8 and 3.0.9 the HttpOnly attribute is not set on a cookie. This allows the cookie's value to be read or set by client-side JavaScript. | ||||
| CVE-2021-34562US | medium6.1 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway 3.0.8 it is possible to inject arbitrary JavaScript into the application's response. | ||||
| CVE-2021-34561US | high8.8 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.8 serious issue exists, if the application is not externally accessible or uses IP-based access restrictions. Attackers can use DNS Reb… | ||||
| CVE-2021-34560US | low2.1 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.9 a form contains a password field with autocomplete enabled. The stored credentials can be captured by an attacker who gains control o… | ||||
| CVE-2021-34559US | medium5.3 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.8 a vulnerability may allow remote attackers to rewrite links and URLs in cached pages to arbitrary strings. | ||||
| CVE-2021-33555US | high7.5 | — | ||
In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.7 the filename parameter is vulnerable to unauthenticated path traversal attacks, enabling read access to arbitrary files on the server… | ||||
| CVE-2020-7656US | medium6.1 | Exploit | ||
jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace characte… | ||||
| CVE-2020-11022US | medium6.1 | Exploit | ||
In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append… | ||||
| CVE-2020-11023US | medium6.1OT critical | KEV | ||
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's… | ||||
| CVE-2019-11358US | medium6.1 | Exploit | ||
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source ob… | ||||
| CVE-2016-10707US | high7.5 | — | ||
jQuery 3.0.0-rc.1 is vulnerable to Denial of Service (DoS) due to removing a logic that lowercased attribute names. Any attribute getter using a mixed-cased name for boolean attrib… | ||||
| CVE-2015-9251US | medium6.1 | Exploit | ||
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses… | ||||
| CVE-2012-6708US | medium6.1 | Exploit | ||
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerab… | ||||
| CVE-2014-6071US | medium6.1 | — | ||
jQuery 1.4.2 allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to use of the text method inside after. | ||||
| CVE-2011-4969US | medium4.3 | — | ||
Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a c… | ||||
| CVE-2013-0169US | low2.6 | Exploit | ||
The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a… | ||||
| CVE-2007-2379US | medium5.0 | — | ||
The jQuery framework exchanges data using JavaScript Object Notation (JSON) without an associated protection scheme, which allows remote attackers to obtain the data via a web page… | ||||
references
External citations — patches, advisories, analysis.
remediations (38)
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
- MitigationWHA-GW-F2D2-0-AS- Z2-ETH.EIP
If remote access is required, use secure methods such as virtual private networks (VPNs).
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan