CVE-2019-8982

9.6 CRITICAL

📋 TL;DR

This vulnerability in WaveMaker Studio 6.6 allows attackers to read local files and perform server-side request forgery (SSRF) attacks by manipulating the download parameter. It affects organizations using vulnerable versions of WaveMaker Studio for application development. The high CVSS score reflects the potential for significant data exposure.

💻 Affected Systems

Products:
  • WaveMaker Studio
Versions: 6.6 and likely earlier versions
Operating Systems: All platforms running WaveMaker Studio
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the StudioService.java component handling file download requests.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of server files including configuration files, credentials, and sensitive data, plus ability to attack internal services via SSRF.

🟠

Likely Case

Unauthorized access to local files containing application source code, configuration data, or credentials stored on the server.

🟢

If Mitigated

Limited impact with proper network segmentation and file system permissions restricting access to sensitive files.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit code is publicly available and demonstrates both local file disclosure and SSRF capabilities.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.7 or later

Vendor Advisory: https://www.wavemaker.com/security-advisory/

Restart Required: Yes

Instructions:

1. Upgrade WaveMaker Studio to version 6.7 or later. 2. Restart the WaveMaker Studio service. 3. Verify the fix by testing the vulnerable endpoint.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement input validation to restrict the 'inUrl' parameter to safe values

Configure web application firewall rules to block requests containing file:// or internal IP patterns in the inUrl parameter

Network Segmentation

all

Isolate WaveMaker Studio from sensitive internal networks

Configure firewall rules to restrict outbound connections from WaveMaker Studio server

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate WaveMaker Studio from sensitive systems
  • Deploy a web application firewall with rules blocking file:// protocols and internal IP ranges in URL parameters

🔍 How to Verify

Check if Vulnerable:

Test the /studioService.download endpoint with file:///etc/passwd in the inUrl parameter

Check Version:

Check WaveMaker Studio version in administration console or configuration files

Verify Fix Applied:

Attempt the same test after patching - should return error or no data

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests to /studioService.download with file:// or internal IP addresses in parameters
  • Unusual file access patterns from WaveMaker Studio process

Network Indicators:

  • Outbound connections from WaveMaker Studio to internal services not normally accessed
  • Requests to internal IP ranges from external sources

SIEM Query:

source="wavemaker.log" AND (uri="/studioService.download" AND (param="file://" OR param="192.168." OR param="10." OR param="172."))

🔗 References

📤 Share & Export