LiveActive security incident?Get immediate response
CVE Record

CVE-2024-1979: Quarkus: information leak in annotation

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.

LowCVSS 3.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Under specific CI conditions, affected Red Hat builds of Quarkus may unintentionally publish Git credentials in an annotation. Anyone able to access the exposed data could threaten the associated repository. Overall severity is low, but leaked credentials may require immediate containment if they carry meaningful repository permissions.

Executive priority

Treat as a routine low-severity update unless credential exposure is found. If CI outputs contain live Git credentials, escalate promptly: revoke them, review repository activity, and assess whether source code, releases, or pipeline configuration could have been accessed.

Technical view

CVE-2024-1979 is a CWE-200 information disclosure affecting specified Red Hat Quarkus builds and the Quarkus Kubernetes deployment package. It has CVSS 3.1 score 3.5 (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N). The bundle identifies confidentiality exposure without direct integrity or availability impact.

Likely exposure

Exposure is most likely where affected Quarkus components are used in CI processes that generate or publish annotations containing Git credential data. The bundle specifically lists Red Hat build 3.2.11.Final-redhat-00001 and Red Hat build of Quarkus 2, but does not provide complete affected or fixed version boundaries.

Exploitation context

The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation. Exploitation requires particular CI conditions and some existing privilege, reflected by high attack complexity and low privileges required. Absence from KEV does not prove exploitation has never occurred.

Researcher notes

The bundle establishes conditional credential disclosure but does not describe the precise triggering configuration, complete version range, fixed versions, or demonstrated attacks. Validation should focus on affected Red Hat Quarkus deployments, CI-generated annotations, and credential audit evidence. Avoid treating generic upstream Quarkus installations as affected without vendor confirmation.

Mitigation direction

  • Review and apply Red Hat guidance in RHSA-2024:1662 for affected builds.
  • Remove exposed credentials from annotations, CI outputs, artifacts, logs, and other published locations.
  • Revoke and rotate any Git credentials that may have been disclosed.
  • Restrict replacement credentials to the minimum repository permissions required.
  • Review vendor guidance for confirmed fixed versions before changing dependencies.

Validation and detection

  • Inventory Quarkus versions and the Kubernetes deployment packages used by CI pipelines.
  • Inspect generated annotations and published CI outputs for Git credentials or secret-bearing URLs.
  • Review repository audit logs for suspicious activity involving potentially exposed credentials.
  • Confirm affected credentials were revoked and replacements have least-privilege permissions.
  • After remediation, rerun a controlled CI build and verify credentials are absent from outputs.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-1979 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.5CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N1.81.4redhat

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2024-1979Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Reported to Red Hat.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorquarkusquarkus, 0unaffected
Red HatRed Hat build of Quarkus 3.2.11.Finalio.quarkus/quarkus-kubernetes-deployment, 3.2.11.Final-redhat-00001affected
Red HatRed Hat build of Quarkusquarkus-kubernetes-deploymentaffected
Weakness

CWE details

CWE-200

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs