CVE-2024-45404
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 · uneditedOpenCTI is an open-source cyber threat intelligence platform. In versions below 6.2.18, because the function to limit the rate of OTP does not exist, an attacker with valid credentials or a malicious user who commits internal fraud can break through the two-factor authentication and hijack the account. This is because the otpLogin mutation does not implement One Time Password rate limiting. As of time of publication, it is unknown whether a patch is available.
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 confidenceOpenCTI versions below 6.2.18 lack rate limiting on the otpLogin GraphQL mutation, allowing attackers to brute-force one-time passwords. An attacker with valid credentials can bypass two-factor authentication and hijack accounts through unlimited OTP retry attempts.
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< 6.2.18CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenCTI installationLocate OpenCTI instances by checking running processes, Docker containers, or web services on common ports (4000 is the default). Query system processes or container orchestration for 'opencti' or 'citeum' processes.Affected if OpenCTI is found running on the system
-
Determine installed OpenCTI versionCheck the version by querying the GraphQL API endpoint (typically at /graphql), reviewing Docker image tags, checking the .env configuration file, or examining package.json if accessible in the installation directory.Affected if The installed version is below 6.2.18 (e.g., 6.2.17, 6.2.0, 5.x.x, etc.)
-
Verify GraphQL otpLogin mutation is exposedSend a POST request to the GraphQL endpoint with a query containing the otpLogin mutation to confirm it accepts OTP authentication attempts. Example: curl -X POST http://HOST:PORT/graphql -H 'Content-Type: application/json' -d '{"query":"mutation otpLogin($input: OtpLoginInput) { otpLogin(input: $input) { token } }"}'Affected if The otpLogin mutation responds and accepts input without immediate rejection or rate limiting headers
-
Confirm lack of rate limiting on otpLoginSend multiple rapid authentication requests (10-20) to the otpLogin mutation from the same source and observe: 1) No HTTP 429 (Too Many Requests) responses, 2) No account lockout or temporary suspension, 3) No CAPTCHA challenge presented, 4) All requests processed normally.Affected if All requests are processed without any throttling, blocking, or challenge being triggered after multiple attempts
You are affected if OpenCTI version is below 6.2.18 AND the GraphQL otpLogin mutation is accessible without rate limiting enforcement.
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.
dbcve · scoped6.2.18
Implement rate limiting on the otpLogin mutation (e.g., limit to 3-5 attempts per IP/user per time window) and add account lockout after failed attempts. Consider CAPTCHA or temporary account suspension until a formal patch is released.
6.2.18
- Backup your current OpenCTI installation and database before upgrading
- Upgrade OpenCTI to version 6.2.18 or later
- After upgrade, verify the platform is running correctly
- Confirm the otpLogin mutation now includes rate limiting protections
- Test that 2FA authentication works properly with the rate limiting in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45404 — 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-2024-45404 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