[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fc5dEUfw4S8tUvIeVDlW8Ry1uYUd_bCzI31eab5-feio":3,"g5a-ex:oracle\u002Fhyperion_infrastructure_technology@*":113,"g5a-family:oracle\u002Fhyperion_infrastructure_technology":115},{"success":4,"data":5},true,{"product":6,"versions":30,"topVulnerabilitiesByEpss":36,"kevVulnerabilities":90,"seoMetadata":91,"meta":110},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":29},"oracle","hyperion_infrastructure_technology",5,34,0,"2022-01-18",[14,18,21,24,27],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},"11.1.2.4",20,false,{"version":19,"cve_count":20,"kev_count":11,"has_kev":17},"11.1.2.6.0",2,{"version":22,"cve_count":23,"kev_count":11,"has_kev":17},"11.2.5.0",3,{"version":25,"cve_count":26,"kev_count":11,"has_kev":17},"11.2.6.0",1,{"version":28,"cve_count":20,"kev_count":11,"has_kev":17},"11.2.7.0","Hyperion Infrastructure Technology by Oracle is a technology product with 5 tracked versions and 34 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[31,32,33,34,35],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},{"version":19,"cve_count":20,"kev_count":11,"has_kev":17},{"version":22,"cve_count":23,"kev_count":11,"has_kev":17},{"version":25,"cve_count":26,"kev_count":11,"has_kev":17},{"version":28,"cve_count":20,"kev_count":11,"has_kev":17},[37,45,52,58,63,68,72,77,81,85],{"cveId":38,"description":39,"publishedDate":40,"cvssScore":41,"cvssVersion":42,"severity":43,"isKev":17,"epssScore":44},"CVE-2021-45105","Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.","2021-12-18",5.9,"v3.1","Medium",0.99999,{"cveId":46,"description":47,"publishedDate":48,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":17,"epssScore":51},"CVE-2020-11984","Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE","2020-08-07",9.8,"Critical",0.90039,{"cveId":53,"description":54,"publishedDate":48,"cvssScore":55,"cvssVersion":42,"severity":56,"isKev":17,"epssScore":57},"CVE-2020-9490","Apache HTTP Server versions 2.4.20 to 2.4.43. A specially crafted value for the 'Cache-Digest' header in a HTTP\u002F2 request would result in a crash when the server actually tries to HTTP\u002F2 PUSH a resource afterwards. Configuring the HTTP\u002F2 feature via \"H2Push off\" will mitigate this vulnerability for unpatched servers.",7.5,"High",0.88844,{"cveId":59,"description":60,"publishedDate":61,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":17,"epssScore":62},"CVE-2019-2729","Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H).","2019-06-19",0.8883,{"cveId":64,"description":65,"publishedDate":66,"cvssScore":55,"cvssVersion":42,"severity":56,"isKev":17,"epssScore":67},"CVE-2021-4104","JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","2021-12-14",0.80599,{"cveId":69,"description":70,"publishedDate":12,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":17,"epssScore":71},"CVE-2022-23305","By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.",0.66537,{"cveId":73,"description":74,"publishedDate":12,"cvssScore":75,"cvssVersion":42,"severity":56,"isKev":17,"epssScore":76},"CVE-2022-23302","JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.",8.8,0.63556,{"cveId":78,"description":79,"publishedDate":48,"cvssScore":55,"cvssVersion":42,"severity":56,"isKev":17,"epssScore":80},"CVE-2020-11993","Apache HTTP Server versions 2.4.20 to 2.4.43 When trace\u002Fdebug was enabled for the HTTP\u002F2 module and on certain traffic edge patterns, logging statements were made on the wrong connection, causing concurrent use of memory pools. Configuring the LogLevel of mod_http2 above \"info\" will mitigate this vulnerability for unpatched servers.",0.56448,{"cveId":82,"description":83,"publishedDate":12,"cvssScore":75,"cvssVersion":42,"severity":56,"isKev":17,"epssScore":84},"CVE-2022-23307","CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.",0.54411,{"cveId":86,"description":87,"publishedDate":88,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":17,"epssScore":89},"CVE-2019-13990","initDocumentParser in xml\u002FXMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.","2019-07-26",0.16628,[],{"title":92,"metaDescription":93,"keywords":94,"structuredData":95},"Hyperion Infrastructure Technology by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Hyperion Infrastructure Technology by Oracle covering 5 versions with 34 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Hyperion Infrastructure Technology vulnerabilities, Hyperion Infrastructure Technology security, Hyperion Infrastructure Technology CVE, Oracle Hyperion Infrastructure Technology, Hyperion Infrastructure Technology threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":96,"@type":97,"name":98,"description":93,"url":99,"manufacturer":100,"applicationCategory":104,"softwareVersion":105,"mainEntity":106},"https:\u002F\u002Fschema.org","SoftwareApplication","Hyperion Infrastructure Technology","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fhyperion_infrastructure_technology",{"@type":101,"name":102,"url":103},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","5 versions tracked",{"@type":107,"name":108,"description":109,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Hyperion Infrastructure Technology Security Vulnerabilities","Security vulnerabilities affecting Hyperion Infrastructure Technology by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":111,"apiVersion":112},"2026-10-17T19:17:56.403Z","3.0",{"rows":114,"total":11,"capped":17,"failed":11},[],[]]