[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fzT7gpQk-cNO3wTeF5r0Ewq79S7ZkjgL9SV3UPeVR_A4":3,"g5a-family:netapp\u002Fh500e_firmware":131,"g5a-ex:netapp\u002Fh500e_firmware@*":132},{"success":4,"data":5},true,{"product":6,"versions":15,"topVulnerabilitiesByEpss":16,"kevVulnerabilities":80,"seoMetadata":109,"meta":128},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":14},"netapp","h500e_firmware",0,148,3,"2022-05-26",[],"H500e Firmware by Netapp is a technology product and 148 known security vulnerabilities including 3 CISA Known Exploited Vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[],[17,26,33,38,44,51,57,63,68,74],{"cveId":18,"description":19,"publishedDate":20,"cvssScore":21,"cvssVersion":22,"severity":23,"isKev":24,"epssScore":25},"CVE-2020-11022","In jQuery versions greater than or equal to 1.2 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(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.","2020-04-29",6.1,"v3.1","Medium",false,0.99215,{"cveId":27,"description":28,"publishedDate":29,"cvssScore":30,"cvssVersion":22,"severity":31,"isKev":4,"epssScore":32},"CVE-2022-0847","A flaw was found in the way the \"flags\" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.","2022-03-10",7.8,"High",0.92795,{"cveId":34,"description":35,"publishedDate":20,"cvssScore":36,"cvssVersion":22,"severity":23,"isKev":4,"epssScore":37},"CVE-2020-11023","In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing \u003Coption> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.",6.9,0.84887,{"cveId":39,"description":40,"publishedDate":41,"cvssScore":42,"cvssVersion":22,"severity":31,"isKev":24,"epssScore":43},"CVE-2022-1292","The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).","2022-05-03",7.3,0.82612,{"cveId":45,"description":46,"publishedDate":47,"cvssScore":48,"cvssVersion":22,"severity":49,"isKev":24,"epssScore":50},"CVE-2021-25216","In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for 32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly also to achieve remote code execution. We have determined that standard SPNEGO implementations are available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems, rendering the ISC implementation unnecessary and obsolete. Therefore, to reduce the attack surface for BIND users, we will be removing the ISC SPNEGO implementation in the April releases of BIND 9.11 and 9.16 (it had already been dropped from BIND 9.17). We would not normally remove something from a stable ESV (Extended Support Version) of BIND, but since system libraries can replace the ISC SPNEGO implementation, we have made an exception in this case for reasons of stability and security.","2021-04-29",9.8,"Critical",0.82367,{"cveId":52,"description":53,"publishedDate":54,"cvssScore":55,"cvssVersion":22,"severity":31,"isKev":24,"epssScore":56},"CVE-2022-0435","A stack overflow flaw was found in the Linux kernel's TIPC protocol functionality in the way a user sends a packet with malicious content where the number of domain member nodes is higher than the 64 allowed. This flaw allows a remote user to crash the system or possibly escalate their privileges if they have access to the TIPC network.","2022-03-25",8.8,0.6777,{"cveId":58,"description":59,"publishedDate":60,"cvssScore":61,"cvssVersion":22,"severity":31,"isKev":24,"epssScore":62},"CVE-2021-22901","curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP\u002F1.1 connection or multiplexed HTTP\u002F2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.","2021-06-11",8.1,0.63531,{"cveId":64,"description":65,"publishedDate":66,"cvssScore":48,"cvssVersion":22,"severity":49,"isKev":24,"epssScore":67},"CVE-2021-43267","An issue was discovered in net\u002Ftipc\u002Fcrypto.c in the Linux kernel before 5.14.16. The Transparent Inter-Process Communication (TIPC) functionality allows remote attackers to exploit insufficient validation of user-supplied sizes for the MSG_CRYPTO message type.","2021-11-02",0.57853,{"cveId":69,"description":70,"publishedDate":71,"cvssScore":72,"cvssVersion":22,"severity":31,"isKev":24,"epssScore":73},"CVE-2021-4044","Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0).","2021-12-14",7.5,0.50099,{"cveId":75,"description":76,"publishedDate":77,"cvssScore":78,"cvssVersion":22,"severity":23,"isKev":24,"epssScore":79},"CVE-2021-41184","jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.","2021-10-26",6.5,0.40768,[81,89,94,104],{"cveId":82,"description":83,"publishedDate":54,"cvssScore":30,"severity":31,"isKev":4,"epssScore":84,"cisaVulnName":85,"cisaDateAdded":86,"cisaShortDescription":87,"cisaRequiredAction":88},"CVE-2022-0995","An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s watch_queue event notification subsystem. This flaw can overwrite parts of the kernel state, potentially allowing a local user to gain privileged access or cause a denial of service on the system.",0.08859,"Linux Kernel Out-of-Bounds Write Vulnerability","2026-08-26","Linux Kernel contains an out-of-bounds memory write vulnerability which could allow a local user to gain privileged access or cause a denial of service on the system.","Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.",{"cveId":34,"description":35,"publishedDate":20,"cvssScore":36,"severity":23,"isKev":4,"epssScore":37,"cisaVulnName":90,"cisaDateAdded":91,"cisaShortDescription":92,"cisaRequiredAction":93},"JQuery Cross-Site Scripting (XSS) Vulnerability","2025-01-23","JQuery contains a persistent cross-site scripting (XSS) vulnerability. When passing maliciously formed, untrusted input enclosed in HTML tags, JQuery's DOM manipulators can execute untrusted code in the context of the user's browser.","Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.",{"cveId":95,"description":96,"publishedDate":97,"cvssScore":98,"severity":31,"isKev":4,"epssScore":99,"cisaVulnName":100,"cisaDateAdded":101,"cisaShortDescription":102,"cisaRequiredAction":103},"CVE-2022-0185","A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem Context functionality of the Linux kernel verified the supplied parameters length. An unprivileged (in case of unprivileged user namespaces enabled, otherwise needs namespaced CAP_SYS_ADMIN privilege) local user able to open a filesystem that does not support the Filesystem Context API (and thus fallbacks to legacy handling) could use this flaw to escalate their privileges on the system.","2022-02-11",8.4,0.25151,"Linux Kernel Heap-Based Buffer Overflow Vulnerability","2024-08-21","Linux kernel contains a heap-based buffer overflow vulnerability in the legacy_parse_param function in the Filesystem Context functionality. This allows an attacker to open a filesystem that does not support the Filesystem Context API and ultimately escalate privileges.","Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.",{"cveId":27,"description":28,"publishedDate":29,"cvssScore":30,"severity":31,"isKev":4,"epssScore":32,"cisaVulnName":105,"cisaDateAdded":106,"cisaShortDescription":107,"cisaRequiredAction":108},"Linux Kernel Privilege Escalation Vulnerability","2022-04-25","Linux kernel contains an improper initialization vulnerability where an unprivileged local user could escalate their privileges on the system. This vulnerability has the moniker of \"Dirty Pipe.\"","Apply updates per vendor instructions.",{"title":110,"metaDescription":111,"keywords":112,"structuredData":113},"H500e Firmware by Netapp - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for H500e Firmware by Netapp with 148 tracked vulnerabilities including 0 critical and 3 high-severity issues and 3 CISA KEV vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","H500e Firmware vulnerabilities, H500e Firmware security, H500e Firmware CVE, Netapp H500e Firmware, H500e Firmware threat intelligence, Netapp security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking, H500e Firmware KEV, H500e Firmware exploited vulnerabilities",{"@context":114,"@type":115,"name":116,"description":111,"url":117,"manufacturer":118,"applicationCategory":122,"softwareVersion":123,"mainEntity":124},"https:\u002F\u002Fschema.org","SoftwareApplication","H500e Firmware","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Fnetapp\u002Fh500e_firmware",{"@type":119,"name":120,"url":121},"Organization","Netapp","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fnetapp","Security Software","Multiple versions",{"@type":125,"name":126,"description":127,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","H500e Firmware Security Vulnerabilities","Security vulnerabilities affecting H500e Firmware by Netapp",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":129,"apiVersion":130},"2026-10-18T18:51:49.480Z","3.0",[],{"rows":133,"total":150,"capped":24,"failed":9},[134,138,142,146],{"cveId":82,"name":85,"severity":31,"cvss":30,"added":86,"epss":84,"published":135,"ranges":136,"checked":4,"hits":137,"covers":24},"2022-03-25T19:15:10.52",[],[],{"cveId":34,"name":90,"severity":23,"cvss":36,"added":91,"epss":37,"published":139,"ranges":140,"checked":4,"hits":141,"covers":24},"2020-04-29T21:15:11.743",[],[],{"cveId":95,"name":100,"severity":31,"cvss":98,"added":101,"epss":99,"published":143,"ranges":144,"checked":4,"hits":145,"covers":24},"2022-02-11T18:15:10.89",[],[],{"cveId":27,"name":105,"severity":31,"cvss":30,"added":106,"epss":32,"published":147,"ranges":148,"checked":4,"hits":149,"covers":24},"2022-03-10T17:44:57.283",[],[],4]