[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcnkMTYJgyaTcEZpFvmldw3WOywIZt6uAN30BVPTjOhg":3,"g5a-ex:oracle\u002Fhealthcare_foundation@*":155,"g5a-family:oracle\u002Fhealthcare_foundation":157},{"success":4,"data":5},true,{"product":6,"versions":54,"topVulnerabilitiesByEpss":72,"kevVulnerabilities":132,"seoMetadata":133,"meta":152},{"vendorName":7,"productName":8,"versionCount":9,"totalCves":10,"kevCount":11,"lastCveUpdate":12,"versions":13,"description":53},"oracle","healthcare_foundation",17,12,0,"2022-01-18",[14,18,21,23,25,27,30,32,35,37,39,41,43,45,47,49,51],{"version":15,"cve_count":16,"kev_count":11,"has_kev":17},"7.1",1,false,{"version":19,"cve_count":20,"kev_count":11,"has_kev":17},"7.1.1",3,{"version":22,"cve_count":16,"kev_count":11,"has_kev":17},"7.1.5",{"version":24,"cve_count":16,"kev_count":11,"has_kev":17},"7.2",{"version":26,"cve_count":20,"kev_count":11,"has_kev":17},"7.2.0",{"version":28,"cve_count":29,"kev_count":11,"has_kev":17},"7.2.1",2,{"version":31,"cve_count":29,"kev_count":11,"has_kev":17},"7.2.2",{"version":33,"cve_count":34,"kev_count":11,"has_kev":17},"7.3.0",5,{"version":36,"cve_count":16,"kev_count":11,"has_kev":17},"7.3.1",{"version":38,"cve_count":16,"kev_count":11,"has_kev":17},"8.0.0",{"version":40,"cve_count":16,"kev_count":11,"has_kev":17},"8.0.1",{"version":42,"cve_count":34,"kev_count":11,"has_kev":17},"8.1.0",{"version":44,"cve_count":16,"kev_count":11,"has_kev":17},"8.1.1",{"version":46,"cve_count":11,"kev_count":11,"has_kev":17},"8.2",{"version":48,"cve_count":11,"kev_count":11,"has_kev":17},"8.2.1",{"version":50,"cve_count":11,"kev_count":11,"has_kev":17},"8.2.2",{"version":52,"cve_count":11,"kev_count":11,"has_kev":17},"8.2.3","Healthcare Foundation by Oracle is a technology product with 17 tracked versions and 12 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this product.",[55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71],{"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":16,"kev_count":11,"has_kev":17},{"version":24,"cve_count":16,"kev_count":11,"has_kev":17},{"version":26,"cve_count":20,"kev_count":11,"has_kev":17},{"version":28,"cve_count":29,"kev_count":11,"has_kev":17},{"version":31,"cve_count":29,"kev_count":11,"has_kev":17},{"version":33,"cve_count":34,"kev_count":11,"has_kev":17},{"version":36,"cve_count":16,"kev_count":11,"has_kev":17},{"version":38,"cve_count":16,"kev_count":11,"has_kev":17},{"version":40,"cve_count":16,"kev_count":11,"has_kev":17},{"version":42,"cve_count":34,"kev_count":11,"has_kev":17},{"version":44,"cve_count":16,"kev_count":11,"has_kev":17},{"version":46,"cve_count":11,"kev_count":11,"has_kev":17},{"version":48,"cve_count":11,"kev_count":11,"has_kev":17},{"version":50,"cve_count":11,"kev_count":11,"has_kev":17},{"version":52,"cve_count":11,"kev_count":11,"has_kev":17},[73,81,87,92,98,104,108,114,120,126],{"cveId":74,"description":75,"publishedDate":76,"cvssScore":77,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":80},"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":82,"description":83,"publishedDate":84,"cvssScore":85,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":86},"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,0.99215,{"cveId":88,"description":89,"publishedDate":90,"cvssScore":85,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":91},"CVE-2019-11358","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 object contained an enumerable __proto__ property, it could extend the native Object.prototype.","2019-04-20",0.8682,{"cveId":93,"description":94,"publishedDate":12,"cvssScore":95,"cvssVersion":78,"severity":96,"isKev":17,"epssScore":97},"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.",9.8,"Critical",0.66537,{"cveId":99,"description":100,"publishedDate":12,"cvssScore":101,"cvssVersion":78,"severity":102,"isKev":17,"epssScore":103},"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,"High",0.63556,{"cveId":105,"description":106,"publishedDate":12,"cvssScore":101,"cvssVersion":78,"severity":102,"isKev":17,"epssScore":107},"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":109,"description":110,"publishedDate":111,"cvssScore":85,"cvssVersion":112,"severity":79,"isKev":17,"epssScore":113},"CVE-2015-9251","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\u002Fjavascript responses to be executed.","2018-01-18","v3.0",0.29726,{"cveId":115,"description":116,"publishedDate":117,"cvssScore":118,"cvssVersion":78,"severity":102,"isKev":17,"epssScore":119},"CVE-2019-10086","In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.","2019-08-20",7.3,0.28384,{"cveId":121,"description":122,"publishedDate":123,"cvssScore":124,"cvssVersion":78,"severity":96,"isKev":17,"epssScore":125},"CVE-2020-1953","Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML includes special statements. Apache Commons Configuration versions 2.2, 2.3, 2.4, 2.5, 2.6 did not change the default settings of this library. So if a YAML file was loaded from an untrusted source, it could therefore load and execute code out of the control of the host application.","2020-03-13",10,0.06323,{"cveId":127,"description":128,"publishedDate":129,"cvssScore":130,"cvssVersion":78,"severity":79,"isKev":17,"epssScore":131},"CVE-2021-28657","A carefully crafted or corrupt file may trigger an infinite loop in Tika's MP3Parser up to and including Tika 1.25. Apache Tika users should upgrade to 1.26 or later.","2021-03-31",5.5,0.02739,[],{"title":134,"metaDescription":135,"keywords":136,"structuredData":137},"Healthcare Foundation by Oracle - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Healthcare Foundation by Oracle covering 17 versions with 12 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Healthcare Foundation vulnerabilities, Healthcare Foundation security, Healthcare Foundation CVE, Oracle Healthcare Foundation, Healthcare Foundation threat intelligence, Oracle security, product security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":138,"@type":139,"name":140,"description":135,"url":141,"manufacturer":142,"applicationCategory":146,"softwareVersion":147,"mainEntity":148},"https:\u002F\u002Fschema.org","SoftwareApplication","Healthcare Foundation","https:\u002F\u002Fprecursorintelligence.com\u002Fvulnerabilities\u002Ftechnologies\u002Fvendors\u002Foracle\u002Fhealthcare_foundation",{"@type":143,"name":144,"url":145},"Organization","Oracle","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Foracle","Security Software","17 versions tracked",{"@type":149,"name":150,"description":151,"vulnerabilityCount":10,"dateModified":12},"SecurityVulnerability","Healthcare Foundation Security Vulnerabilities","Security vulnerabilities affecting Healthcare Foundation by Oracle",{"totalVersions":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":12,"generatedAt":153,"apiVersion":154},"2026-10-17T12:38:04.501Z","3.0",{"rows":156,"total":11,"capped":17,"failed":11},[],[]]