Build Of QuarkusApplication · Redhat
CVE-2023-0044
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIf the Quarkus Form Authentication session cookie Path attribute is set to `/` then a cross-site attack may be initiated which might lead to the Information Disclosure. This attack can be prevented with the Quarkus CSRF Prevention feature.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceQuarkus Form Authentication stores session cookies with a Path attribute of `/`, which allows these cookies to be sent to all paths on the domain. This misconfiguration enables cross-site attacks where malicious sites can trigger authenticated requests to the vulnerable application, potentially leading to information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Build Of QuarkusApplication
all versions< 2.13.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Quarkus installation and versionCheck your project for Quarkus dependencies (e.g., examine pom.xml, build.gradle, or the quarkus --version CLI output). Identify the exact Quarkus version number.Affected if The installed Quarkus version is less than 2.13.7, or you are using Red Hat Build of Quarkus (any version).
-
Verify form authentication is enabledExamine your Quarkus application configuration (application.properties or application.yaml) for authentication mechanisms. Look for properties such as quarkus.http.auth.form.enabled=true or similar form-based authentication configuration.Affected if Form-based authentication is enabled in the Quarkus application.
-
Inspect session cookie configurationReview your Quarkus HTTP configuration for session cookie settings. Check for properties like quarkus.http.session.cookie.path or examine the actual Set-Cookie headers in HTTP responses from your application when authenticated.Affected if The session cookie Path attribute is set to "/" (the default), meaning the cookie is sent to all paths on the domain.
-
Check for CSRF token implementationReview your application's form handling code and configuration to determine if Quarkus CSRF prevention tokens are implemented. Look for quarkus.csrf.token.enabled settings or anti-CSRF token fields in your forms.Affected if CSRF prevention is NOT enabled or not properly implemented, leaving the application vulnerable to cross-site attacks exploiting the broad cookie scope.
You are affected if you run Quarkus with form authentication enabled, the Quarkus version is less than 2.13.7 (or is Red Hat Build of Quarkus), and CSRF token protection is not implemented.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.13.7
Enable Quarkus's built-in CSRF Prevention feature to add anti-CSRF tokens to forms and validate them on submission, preventing cross-site attack vectors from abusing the overly-broad session cookie scope.
Quarkus 2.13.7 or later
- 1. Identify the current Quarkus version in your project by checking your pom.xml or build.gradle file
- 2. Update the Quarkus version in your dependency management to version 2.13.7 or later
- 3. Rebuild and test your application to verify the fix is applied
- 4. Alternatively, enable Quarkus CSRF Prevention feature as an additional mitigation measure
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Of Quarkus
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data