CVE-2019-0020

10.0 CRITICAL

📋 TL;DR

Juniper ATP versions before 5.0.3 contain hard-coded credentials in the Web Collector instance, allowing attackers to gain full administrative control of affected systems. This affects all installations running vulnerable versions, regardless of configuration. The vulnerability is critical due to the complete system compromise it enables.

💻 Affected Systems

Products:
  • Juniper Networks Advanced Threat Prevention (ATP)
Versions: 5.0 versions prior to 5.0.3
Operating Systems: Juniper ATP OS
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of affected versions are vulnerable regardless of configuration settings.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system takeover with administrative privileges, allowing data exfiltration, lateral movement, ransomware deployment, and persistent backdoor installation.

🟠

Likely Case

Unauthorized administrative access leading to security policy modification, data theft, and use as pivot point for network attacks.

🟢

If Mitigated

Limited impact if isolated in segmented network with strict access controls, but still represents significant risk due to hard-coded credentials.

🌐 Internet-Facing: HIGH - Any internet-facing vulnerable instance can be directly compromised without authentication.
🏢 Internal Only: HIGH - Internal attackers or compromised systems can exploit this to gain full control of ATP systems.

🎯 Exploit Status

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

Exploitation requires only knowledge of hard-coded credentials, making this trivial to exploit once credentials are discovered.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 5.0.3 or later

Vendor Advisory: https://kb.juniper.net/JSA10918

Restart Required: Yes

Instructions:

1. Download Juniper ATP 5.0.3 or later from Juniper support portal. 2. Backup current configuration. 3. Apply the update via the ATP web interface or CLI. 4. Reboot the system as required. 5. Verify successful update and functionality.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate ATP systems in dedicated security zone with strict firewall rules limiting access to management interfaces.

Access Control Lists

all

Implement strict source IP restrictions on ATP management interfaces to limit potential attackers.

🧯 If You Can't Patch

  • Immediately isolate affected systems from production networks and internet access
  • Implement strict network segmentation and monitor for unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check ATP version via web interface or CLI: show version. If version is 5.0, 5.0.1, or 5.0.2, system is vulnerable.

Check Version:

show version

Verify Fix Applied:

After patching, verify version is 5.0.3 or later using show version command and test that hard-coded credentials no longer work.

📡 Detection & Monitoring

Log Indicators:

  • Failed authentication attempts followed by successful login with default credentials
  • Unusual administrative activity from unexpected sources
  • Configuration changes from unauthorized users

Network Indicators:

  • Unauthorized access to ATP management ports (default 443)
  • Traffic patterns indicating data exfiltration from ATP systems

SIEM Query:

source="juniper_atp" AND (event_type="authentication" AND result="success" AND user="default_admin") OR (event_type="configuration_change" AND user!="authorized_user")

🔗 References

📤 Share & Export