dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11401

MEDIUM · 5.3 CVSS v4.0 Published 2024-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Rapid7 Insight Platform versions prior to November 13th 2024, suffer from a privilege escalation vulnerability whereby, due to a lack of authorization checks, an attacker can successfully update the password policy in the platform settings as a standard user by crafting an API (the functionality was not possible through the platform's User Interface). This vulnerability has been fixed as of November 13th 2024.

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 confidence

A privilege escalation vulnerability in Rapid7 Insight Platform allows standard users to bypass UI authorization controls and update password policy settings via direct API calls. The lack of server-side authorization validation on the API endpoint enables any authenticated user to modify security policies they should not have access to.

MitigationUpgrade to Rapid7 Insight Platform version released on or after November 13th, 2024 to obtain the patched build that includes proper authorization checks on API endpoints.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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 Rapid7 Insight Platform installation
    Locate the Insight Platform components on your system or check your deployed software inventory for Rapid7 Insight Platform
    Affected if The platform is not present in your environment
  2. Determine installed version
    Check the installed version of Rapid7 Insight Platform through the platform UI, command line, or configuration files, then compare against the November 13th, 2024 release date
    Affected if The installed version was released before November 13th, 2024 (or the exact version cannot be determined to be post-patch)
  3. Verify API access is enabled
    Confirm that the API functionality is enabled in the platform settings and that standard (non-admin) users have API authentication credentials
    Affected if Standard users have active API access credentials
  4. Test authorization on password policy API endpoint
    Using a standard user account, attempt to make an API call to the password policy settings endpoint (e.g., PUT/POST to the policy configuration API)
    Affected if A standard user can successfully modify password policy settings via direct API call without receiving a 403 Forbidden or authorization error

If Rapid7 Insight Platform is running a version released before November 13th, 2024 and allows authenticated standard users to modify password policy settings through direct API calls, the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Rapid7 Insight Platform version released on or after November 13th, 2024 to obtain the patched build that includes proper authorization checks on API endpoints.

Recommended fix High confidence

Fixed as of November 13th, 2024 (contact Rapid7 support to confirm your instance received the patch)

  1. Confirm with Rapid7 support that your Insight Platform instance has received the November 13th 2024 security update
  2. Verify that the authorization fix is active by attempting to confirm standard users cannot modify password policy via API (this should now fail with appropriate authorization error)
  3. Review platform audit logs around the time of the fix to check for any unauthorized password policy modifications that may have occurred prior to the patch
  4. If you suspect exploitation occurred before the fix, review and reset any affected credentials or policies
  5. Ensure your organization's security policies align with the password policy settings currently in place

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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