Approved changes feed: RSS · Atom

cpe:2.3:a:oracle:healthcare_foundation:8.1.0:*:*:*:*:*:*:*

part: a version: 8.1.0 update: *

VendorOracle (3509f9eb-d8a0-57da-b153-b8021021b133)
ProductHealthcare Foundation (9c86f85d-6f5a-5324-aafb-795b3be833ca)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-23307 vulnerable 2026-06-08 05:40:56.954349 A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution.
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.
Published: 2022-01-18T15:25:23.000Z
Updated: 2026-05-27T13:44:43.452Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-23305 vulnerable 2026-06-08 05:40:56.948814 SQL injection in JDBC Appender in Apache Log4j V1
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.
Published: 2022-01-18T15:25:22.000Z
Updated: 2026-05-27T13:40:57.853Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-23302 vulnerable 2026-06-08 05:40:56.933547 Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
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.
Published: 2022-01-18T15:25:20.000Z
Updated: 2026-05-27T13:46:05.384Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-28657 vulnerable 2026-06-08 05:31:24.697962 Infinite loop in Apache Tika's MP3 parser
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.
Published: 2021-03-31T07:35:14.000Z
Updated: 2025-02-13T16:27:59.935Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-10219 vulnerable 2026-06-08 05:12:22.682142 Details available
MEDIUM (6.5)
A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.
Published: 2019-11-08T14:46:03.000Z
Updated: 2025-07-07T13:55:51.360Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.