Bug 2266690 (CVE-2024-1979)

Summary:	CVE-2024-1979 quarkus: information leak in annotation
Product:	[Other] Security Response	Reporter:	Nick Tait <ntait>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	anstephe, avibelli, bgeorges, chazlett, clement.escoffier, dandread, dkreling, gsmet, jcechace, jmartisk, lthon, max.andersen, mosmerov, olubyans, pgallagh, pjindal, probinso, rruss, rsvoboda, sausingh, sbiarozk, sdouglas, security-response-team, tqvarnst
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	quarkus 3.7.3	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in Quarkus. In certain conditions related to the CI process, git credentials could be inadvertently published, which could put the git repository at risk.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-13 16:00:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2266699

Description Nick Tait 2024-02-28 18:11:17 UTC

The problem described at https://github.com/quarkusio/quarkus/issues/38055 has potential security impact.

Note that this is NOT a runtime CVE and that it will happen in very
specific circumstances but it could lead to Git credentials leaking and
thus your Git repository being at risk.

- If you are in an environment where you have a token in the Git URL of the
Quarkus project you are building (which unfortunately sometimes happens on
CI as it's the easiest way to authenticate)
- if you build with an extension that generates a Kubernetes descriptor
(e.g. Kubernetes or OpenShift extension)
- if you publish the descriptor somehow (for instance as a build artifact
attached to your CI build - for instance GitHub Actions artifacts)

Then there's a risk for your token to be leaked and your Git repository
potentially compromised.

The fix is simple: https://github.com/quarkusio/quarkus/pull/38748/files

Comment 8 errata-xmlrpc 2024-04-03 10:53:26 UTC

This issue has been addressed in the following products:

  Red Hat build of Quarkus 3.2.11

Via RHSA-2024:1662 https://access.redhat.com/errata/RHSA-2024:1662