Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-2700 high CVSS 7.0

Vulnerability in io.quarkus:quarkus-core (CVE-2024-2700)

Summary

Vulnerability in io.quarkus:quarkus-core (CVE-2024-2700). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.2.12.Final or later.

Original description

The description as published by the source.

A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application's build. Thus, running the resulting application inherits the values captured at build time.

However, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application. It may lead to dangerous behavior if the application does not override these values.

This behavior only happens for configuration properties from the quarkus.* namespace. So, application-specific properties are not captured.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-2700 has been found in io.quarkus:quarkus-core.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: upgrade io.quarkus:quarkus-core to 3.2.12.Final or later.
If unsure, ask your IT team or search "io.quarkus:quarkus-core CVE-2024-2700" on the vendor's site.

CVE-2024-2700 (io.quarkus:quarkus-core) — CWE-526 / CVSS v3 7.0
Attack vector: local / no user interaction
Patched: 3.2.12.Final — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-526) exists in io.quarkus:quarkus-core.

📍 Affected scope

Check the vendor advisory for the affected versions of io.quarkus:quarkus-core.

🔥 Severity

Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.2.12.Final.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.quarkus:quarkus-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.quarkus:quarkus-core to 3.2.12.Final

    ステージング環境で 3.2.12.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven io.quarkus:quarkus-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.12.Final"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details