CVE-2022-40724
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 · uneditedThe PingFederate Local Identity Profiles '/pf/idprofile.ping' endpoint is vulnerable to Cross-Site Request Forgery (CSRF) through crafted GET requests.
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 PingFederate Local Identity Profiles endpoint '/pf/idprofile.ping' is vulnerable to Cross-Site Request Forgery (CSRF). An attacker can craft malicious GET requests that trick authenticated users into unknowingly performing unauthorized actions on the vulnerable endpoint.
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>= 10.3.0, <= 10.3.11>= 11.0.0, <= 11.0.6>= 11.1.0, <= 11.1.5>= 11.2.0, <= 11.2.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PingFederate installed versionLocate the version file typically at <install_dir>/pingfederate/VERSION or check the admin console under System > Protocol Settings > Version Info. Compare against affected ranges: 10.3.0-10.3.11, 11.0.0-11.0.6, 11.1.0-11.1.5, 11.2.0-11.2.2Affected if Installed version falls within any of the affected version ranges
-
Confirm Local Identity Profiles is enabledAccess the PingFederate admin console and navigate to Local Identity > Local Identity Profiles, or inspect the deployed configuration files in the <install_dir>/pingfederate/server/default/data/config-store directory for idp.profile.local.identity configurationAffected if Local Identity Profiles feature is configured and active in the environment
-
Verify anti-CSRF token requirement for /pf/idprofile.pingExamine the HTML source of the Local Identity profile page (accessible at /pf/idprofile.ping) and search for a hidden CSRF token field or anti-CSRF token in the form submissionAffected if The endpoint renders without any anti-CSRF token parameter in the form (no _csrf or similar token field present)
Environment is affected if PingFederate version is within the affected ranges AND Local Identity Profiles are enabled AND the /pf/idprofile.ping endpoint lacks anti-CSRF token protection in its forms.
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.
From vendor dataImplement anti-CSRF tokens for the '/pf/idprofile.ping' endpoint and configure SameSite attributes on session cookies to prevent CSRF attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40724 — 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-2022-40724 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