Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-22273

CRITICAL · 9.3 CVSS v4.0 Published 2025-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Application does not limit the number or frequency of user interactions, such as the number of incoming requests. At the "/EPMUI/VfManager.asmx/ChangePassword" endpoint it is possible to perform a brute force attack on the current password in use. This issue affects CyberArk Endpoint Privilege Manager in SaaS version 24.7.1. The status of other versions is unknown. After multiple attempts to contact the vendor we did not receive any answer.

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

CyberArk Endpoint Privilege Manager SaaS version 24.7.1 lacks rate limiting on the /EPMUI/VfManager.asmx/ChangePassword endpoint, allowing unlimited password change attempts. This enables attackers to perform brute force attacks against user passwords without detection or restriction.

MitigationImplement rate limiting, request throttling, and account lockout policies on the ChangePassword endpoint to restrict the number of failed authentication attempts within a given time window.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 CyberArk EPM SaaS version
    Access the CyberArk Endpoint Privilege Manager administration console or check system information to determine the installed SaaS version number
    Affected if version is 24.7.1 or falls within an unpatched version range relative to 24.7.1
  2. Verify ChangePassword endpoint exposure
    Confirm the /EPMUI/VfManager.asmx/ChangePassword web service endpoint is accessible from the network by testing HTTP access to this URL path
    Affected if the endpoint is externally or internally reachable without additional authentication barriers
  3. Check rate limiting configuration
    Review web server or application gateway settings for rate limiting, throttling, or request filtering rules applied to the /EPMUI/VfManager.asmx/ChangePassword endpoint
    Affected if no rate limit, request throttle, or attempt restriction is configured for this endpoint
  4. Review authentication logs for brute force patterns
    Examine CyberArk EPM logs, web server logs, or SIEM alerts for repeated password change requests from single IPs or user accounts targeting the ChangePassword endpoint
    Affected if logs show high volumes of password change attempts without triggering lockout or detection
  5. Verify account lockout policy
    Check CyberArk EPM authentication and account security policies to confirm whether failed password change attempts trigger account lockout or temporary blocking
    Affected if no account lockout or attempt-based blocking is enforced after multiple password change failures

You are affected if CyberArk EPM SaaS version 24.7.1 is running and the ChangePassword endpoint lacks rate limiting or account lockout protections, allowing unlimited password change attempts.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rate limiting, request throttling, and account lockout policies on the ChangePassword endpoint to restrict the number of failed authentication attempts within a given time window.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22273 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22273 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