CVE-2023-39069

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to bypass authentication and gain unauthorized privileges in TheHive and Cortex security platforms when using Active Directory authentication. Attackers can exploit incomplete checks in the AD authentication module to access systems with elevated permissions. Organizations using affected versions with AD authentication enabled are at risk.

💻 Affected Systems

Products:
  • TheHive
  • Cortex
Versions: TheHive v5.0.8 and v4.1.21; Cortex v3.1.6
Operating Systems: All supported platforms
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when Active Directory authentication is configured and enabled. Systems using other authentication methods are not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of TheHive/Cortex instances allowing attackers to access sensitive security data, manipulate investigations, and potentially pivot to other systems in the environment.

🟠

Likely Case

Unauthorized access to security platforms enabling data exfiltration, manipulation of security investigations, and privilege escalation within the affected applications.

🟢

If Mitigated

Limited impact if AD authentication is disabled or proper network segmentation isolates the vulnerable systems from untrusted networks.

🌐 Internet-Facing: HIGH - Remote exploitation possible if systems are exposed to internet or untrusted networks.
🏢 Internal Only: HIGH - Even internally, attackers with network access can exploit this vulnerability to gain unauthorized access.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability is in authentication logic, making exploitation straightforward for attackers with network access to vulnerable systems.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: TheHive v5.0.9+, v4.1.22+; Cortex v3.1.7+

Vendor Advisory: https://github.com/StrangeBeeCorp/Security/blob/main/Security%20advisories/SB-SEC-ADV-2022-001%3A%20Authentication%20bypass%20due%20to%20incomplete%20checks%20in%20the%20Active%20Directory%20authentication%20module.md

Restart Required: Yes

Instructions:

1. Backup your configuration and data. 2. Stop TheHive/Cortex services. 3. Update to patched versions using your package manager or installation method. 4. Restart services. 5. Verify authentication works correctly.

🔧 Temporary Workarounds

Disable Active Directory Authentication

all

Temporarily disable AD authentication and use alternative authentication methods until patching is complete.

Edit configuration files to remove or comment out AD authentication settings
Restart TheHive/Cortex services after configuration changes

Network Segmentation

all

Restrict network access to TheHive/Cortex instances to only trusted IP addresses and networks.

Configure firewall rules to limit access
Use network security groups or ACLs to restrict traffic

🧯 If You Can't Patch

  • Disable Active Directory authentication immediately and use alternative authentication methods
  • Implement strict network access controls to limit which systems can reach the vulnerable applications

🔍 How to Verify

Check if Vulnerable:

Check if using affected versions (TheHive 5.0.8/4.1.21 or Cortex 3.1.6) with AD authentication enabled in configuration.

Check Version:

For TheHive: Check web interface or run 'thehive --version'. For Cortex: Check web interface or run 'cortex --version'.

Verify Fix Applied:

Verify version is updated to patched versions (TheHive 5.0.9+/4.1.22+ or Cortex 3.1.7+) and test AD authentication functionality.

📡 Detection & Monitoring

Log Indicators:

  • Failed authentication attempts followed by successful logins from unexpected sources
  • Authentication events showing privilege escalation
  • Unusual user activity patterns

Network Indicators:

  • Authentication requests to AD endpoints from unexpected sources
  • Traffic patterns indicating enumeration or brute force attempts

SIEM Query:

source="thehive" OR source="cortex" AND (event_type="authentication" AND result="success") AND user NOT IN [expected_users]

🔗 References

📤 Share & Export