OpenCTI's lack of Rate Limit lead to OTP brute forcing

published 2024-12-11 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-41714 , GHSA-hg56-r6hh-56j7 , PYSEC-2024-297

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits: 0; none known

OpenCTI 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.

Patch / fix

fixed in 2

pypi pycti 6.2.18
citeum opencti 6.2.8

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 22 mo ago (2024-12-12)

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-hg56-r6hh-56j7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	pycti	<6.2.18	6.2.18

Affected products

OpenCTI-Platform opencti

Classification

Weakness

CWE-287 Improper Authentication
CWE-307 Improper Restriction of Excessive Authentication Attempts

References

github.com /OpenCTI-Platform/opencti/security/advisories/GHSA-hg56-r6hh-56j7
exploit, vendor-advisory, advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary