CVE-2024-33647
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 · uneditedA vulnerability has been identified in Polarion ALM (All versions < V2404.0). The Apache Lucene based query engine in the affected application lacks proper access controls. This could allow an authenticated user to query items beyond the user's allowed projects.
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 confidenceThe Apache Lucene-based query engine in Polarion ALM versions prior to V2404.0 fails to enforce project-level access controls, allowing any authenticated user to query and retrieve items from projects outside their permitted scope by manipulating Lucene queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Polarion ALM is installedLocate the Polarion ALM installation directory or check system inventory for the Polarion ALM productAffected if Polarion ALM is not present on the system - this CVE does not apply
-
Identify the Polarion ALM versionCheck the installed Polarion ALM version in the product about panel or version fileAffected if The installed version is prior to V2404.0 - the vulnerability exists in those versions
-
Verify Lucene query engine is accessibleConfirm the Lucene-based query functionality is available to authenticated users in the Polarion ALM interfaceAffected if The Lucene query feature is not accessible or not in use - the vulnerability requires this component to be available
-
Test project-level query access controlsAs an authenticated user with limited project permissions, attempt to construct a Lucene query that references items from a project outside your permitted scopeAffected if Users can retrieve items from projects they should not have access to - the access control failure is present
The environment is affected if Polarion ALM version prior to V2404.0 is installed AND the Lucene query engine is accessible to authenticated users.
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 · scopedUpgrade Polarion ALM to version V2404.0 or later which includes proper access control enforcement in the Lucene query engine.
V2404.0 or later
- Back up the current Polarion ALM installation and database before proceeding with the upgrade
- Download Polarion ALM version V2404.0 or later from the official Siemens/Polarion download portal
- Follow the standard Polarion ALM upgrade procedure documented in the installation guide
- After upgrading, verify that the Apache Lucene query engine now properly enforces access controls
- Confirm that users can only query items within their allowed projects
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33647 — 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-2024-33647 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