dbcve.org
Polarion AlmApplication · Siemens

CVE-2024-23813

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 2404.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been identified in Polarion ALM (All versions < V2404.0). The REST API endpoints of doorsconnector of the affected product lacks proper authentication. An unauthenticated attacker could access the endpoints, and potentially execute code.

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 · moderate confidence

Polarion ALM's doorsconnector REST API endpoints lack proper authentication, allowing unauthenticated attackers to directly access these endpoints. The CVSS 9.8 rating and mention of potential code execution indicates this is a critical authentication bypass vulnerability that could allow full system compromise.

MitigationUpgrade Polarion ALM to version V2404.0 or later to obtain the patched authentication implementation for doorsconnector endpoints.

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
Polarion AlmApplication
Affected:< 2404.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Polarion ALM installation and version
    Locate the Polarion installation directory and check the version file or product info. Common locations include the installation root or About dialog within the application. Look for version information in release notes, product metadata, or the administration interface.
    Affected if The installed version of Siemens Polarion ALM is lower than 2404.0
  2. Determine if doorsconnector module is enabled
    Check the Polarion configuration files or administration settings for the doorsconnector component status. Inspect the Polarion configuration XML files or the admin dashboard for doorsconnector module activation.
    Affected if The doorsconnector module is installed and enabled in the Polarion environment
  3. Verify doorsconnector REST API endpoint accessibility
    Attempt to access the doorsconnector REST API endpoints without authentication credentials. Common endpoint patterns include /polarion/doorsconnector/api/ or similar paths under the Polarion web application root. Use a web browser or HTTP client to send an unauthenticated request.
    Affected if The doorsconnector REST API endpoints respond successfully without requiring authentication headers or credentials
  4. Inspect doorsconnector authentication configuration
    Review the Polarion web.xml or security configuration files for doorsconnector endpoint protection settings. Check if these specific endpoints are excluded from authentication requirements in the security constraint definitions.
    Affected if The doorsconnector REST API paths are explicitly excluded from authentication requirements or lack security constraint definitions

You are affected if running Polarion ALM version lower than 2404.0 with the doorsconnector module enabled and its REST API endpoints accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2404.0 or later
Fixed in 2404.0
Interim mitigation

Upgrade Polarion ALM to version V2404.0 or later to obtain the patched authentication implementation for doorsconnector endpoints.

Recommended fix Moderate confidence

V2404.0 (or 2404.0)

  1. 1. Identify current Polarion ALM version by checking the administration console or about page
  2. 2. Plan upgrade to version 2404.0 or later as the fixed release
  3. 3. Back up the current Polarion ALM database and configuration files
  4. 4. Review Siemens Polarion upgrade documentation for the 2404.0 release
  5. 5. Execute the upgrade following the official upgrade procedure
  6. 6. After upgrade, verify that doorsconnector REST API now requires proper authentication
  7. 7. Test that authenticated users can access doorsconnector endpoints while unauthenticated access is denied
  8. 8. Validate in a non-production environment before deploying to production
Caveat Major version upgrades may introduce compatibility changes; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Polarion Alm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23813 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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