VulnerabilityPublished 1 Aug 2024Updated 2 Aug 2024

CVE-2024-41265: cortex · Missing Validation of OpenSSL Certificate

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-41265, organizations should first monitor Cortex vendor communications for official patches or updates addressing the TLS verification flaw and apply them promptly. In the absence of patches, administrators should enforce strict network segmentation and restrict access to Cortex instances to trusted networks only, minimizing exposure to untrusted actors. Implementing network-level TLS interception detection and anomaly monitoring can help identify potential man-in-the-middle attempts. Additionally, organizations should review and harden TLS configurations on Cortex servers, ensuring the use of strong cipher suites and certificate pinning where possible. Employing external TLS proxy solutions that enforce certificate validation can provide an additional layer of defense. Regularly auditing and logging operator request activities will aid in early detection of suspicious behavior. Finally, educating security teams about the risks of improper TLS verification and encouraging vigilance during incident response activities will help reduce the likelihood and impact of exploitation.

Description

A TLS certificate verification issue discovered in cortex v0.42.1 allows attackers to obtain sensitive information via the makeOperatorRequest function.

Impact

The primary impact of CVE-2024-41265 is the unauthorized disclosure of sensitive information due to improper TLS certificate verification. Organizations relying on Cortex for security orchestration risk exposure of confidential data transmitted during operator requests, potentially including authentication tokens, incident details, or other sensitive operational information. This exposure can facilitate further attacks such as credential theft, reconnaissance, or targeted intrusions. The vulnerability does not directly affect data integrity or availability but compromises confidentiality, which is critical in security operations contexts. Exploitation could undermine trust in Cortex's communications, delaying incident response and increasing the risk of successful attacks on the organization. Since the vulnerability requires no authentication or user interaction, it can be exploited by any remote attacker capable of intercepting network traffic, increasing the attack surface. The lack of known exploits in the wild suggests limited current impact, but the potential for future exploitation remains significant. Organizations in sectors with high security demands, such as government, finance, healthcare, and critical infrastructure, face elevated risks due to the sensitive nature of data handled by Cortex.

CWE-599Missing Validation of OpenSSL Certificate (opens in a new tab)
Variant weakness
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
Architecture and Design
Ensure that proper authentication is included in the system design.
Implementation
Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/nyxfqq/1a8237f3f9cf793c6433f08b17d1593c (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 05:36 UTC

WeaknessesCWE-599

Technical details

References

Community reviews

Related threats