Red Hat Integration Camel Quarkus
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:integration_camel_quarkus:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Integration Camel Quarkus (6b3103e4-fe31-5be3-a2bb-0679859736ef) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/apache/camel-quarkus |
purl2cpe | 2026-06-01 10:12:57.285287 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-4853 |
vulnerable | 2026-06-08 06:16:14.736086 |
Quarkus: http security policy bypass
HIGH (8.1)
A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.
Published: 2023-09-20T09:47:32.150Z
Updated: 2025-11-07T10:17:29.266Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41862 |
vulnerable | 2026-06-08 05:49:28.768925 |
Details available
In PostgreSQL, a modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. In certain conditions a server can cause a libpq client to over-read and report an error message containing uninitialized bytes.
Published: 2023-03-03T00:00:00.000Z
Updated: 2025-03-07T16:03:01.364Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0084 |
vulnerable | 2026-06-08 05:39:09.215835 |
Details available
A flaw was found in XNIO, specifically in the notifyReadClosed method. The issue revealed this method was logging a message to another expected end. This flaw allows an attacker to send flawed requests to a server, possibly causing log contention-related performance concerns or an unwanted disk fill-up.
Published: 2022-08-26T17:25:46.000Z
Updated: 2024-08-02T23:18:41.681Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-4104 |
vulnerable | 2026-06-08 05:38:08.344093 |
Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2
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.
Published: 2021-12-14T00:00:00.000Z
Updated: 2026-05-28T19:53:14.378Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3690 |
vulnerable | 2026-06-08 05:33:53.424710 |
Details available
A flaw was found in Undertow. A buffer leak on the incoming WebSocket PONG message may lead to memory exhaustion. This flaw allows an attacker to cause a denial of service. The highest threat from this vulnerability is availability.
Published: 2022-08-23T15:50:35.000Z
Updated: 2024-08-03T17:01:08.307Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3536 |
vulnerable | 2026-06-08 05:33:52.730044 | db.gcve.eu details were skipped to keep the page responsive. | 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.