dbcve.org
PingfederateApplication · Pingidentity

CVE-2024-22377

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 11.3.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The deploy directory in PingFederate runtime nodes is reachable to unauthorized users.

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

The deploy directory in PingFederate runtime nodes is exposed and accessible to unauthorized users without authentication. This allows remote attackers to potentially access sensitive configuration files, deployment artifacts, and system information stored in the deploy directory, which could aid in further attacks against the system.

MitigationRestrict access to the deploy directory by implementing proper authentication and authorization controls at the web server or application level, or relocate the deploy directory outside the web-accessible root.

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
PingfederateApplication
Affected:>= 10.3.0, <= 10.3.13>= 11.0.0, <= 11.0.9>= 11.1.0, <= 11.1.9>= 11.2.0, <= 11.2.8>= 11.3.0, <= 11.3.4= 12.0.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Identify PingFederate installation and version
    Locate the PingFederate installation directory and check the version. Typically, the version can be found in a version.properties file in the installation root, or by checking the admin console for the version number.
    Affected if The installed version falls within the affected ranges: 10.3.0-10.3.13, 11.0.0-11.0.9, 11.1.0-11.1.9, 11.2.0-11.2.8, 11.3.0-11.3.4, or 12.0.0.
  2. Locate the deploy directory
    The deploy directory is typically located in the runtime node installation under the pingfederate/deploy subdirectory. Identify the full path to this directory within your installation.
    Affected if The deploy directory exists in the PingFederate installation path.
  3. Verify if the deploy directory is web-accessible
    Check your web server or reverse proxy configuration to determine whether the deploy directory or its contents are accessible via HTTP/HTTPS. Attempt to access common paths such as /deploy/ or /pf/deploy/ from an external host.
    Affected if The deploy directory is reachable through the web server without requiring authentication.
  4. Test for unauthenticated access to deploy directory contents
    Using a web browser or curl command, attempt to retrieve files from the deploy directory without providing any credentials. Check if files such as XML configuration files, JAR artifacts, or directory listings are returned.
    Affected if The deploy directory contents are served without authentication, exposing configuration files or deployment artifacts.

A user is affected if they are running an affected PingFederate version AND the deploy directory is accessible over the network without authentication, allowing unauthorized disclosure of configuration and deployment artifacts.

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 a release after 11.3.4
Interim mitigation

Restrict access to the deploy directory by implementing proper authentication and authorization controls at the web server or application level, or relocate the deploy directory outside the web-accessible root.

Recommended fix Moderate confidence

11.2.9 (or latest 11.2.x); for older branches: 10.3.14, 11.0.10, 11.1.10 respectively

  1. 1. Identify the currently running PingFederate version from the admin console or runtime node configuration.
  2. 2. For PingFederate 10.3.x: Upgrade to version 10.3.14 or later.
  3. 3. For PingFederate 11.0.x: Upgrade to version 11.0.10 or later.
  4. 4. For PingFederate 11.1.x: Upgrade to version 11.1.10 or later.
  5. 5. For PingFederate 11.2.x: Upgrade to version 11.2.9 or later.
  6. 6. After upgrading, verify that the deploy directory is no longer accessible to unauthenticated users by attempting to access it via HTTP/HTTPS from an unauthorized network location.
  7. 7. Review the PingFederate administrative console to confirm the runtime node is operational and serving legitimate traffic correctly.
Caveat Patch upgrades typically have minimal risk; however, always review release notes for any configuration or behavioral changes before deploying to production.

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

Fix this in Pingfederate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,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 $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22377 — 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-22377 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