CVE-2022-43842

8.6 HIGH

📋 TL;DR

CVE-2022-43842 is a SQL injection vulnerability in IBM Aspera Console versions 3.4.0 through 3.4.2 that allows remote attackers to execute arbitrary SQL commands. This could enable attackers to view, modify, or delete database information, potentially compromising sensitive data. Organizations running affected IBM Aspera Console versions are vulnerable.

💻 Affected Systems

Products:
  • IBM Aspera Console
Versions: 3.4.0 through 3.4.2
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential lateral movement to other systems.

🟠

Likely Case

Data exfiltration of sensitive information stored in the Aspera Console database, including user credentials, file transfer logs, and configuration data.

🟢

If Mitigated

Limited impact with proper network segmentation, database permissions, and input validation controls in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

SQL injection vulnerabilities typically have low exploitation complexity, but specific exploit details for this CVE are not publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.4.3 or later

Vendor Advisory: https://www.ibm.com/support/pages/node/7122632

Restart Required: Yes

Instructions:

1. Download IBM Aspera Console 3.4.3 or later from IBM Fix Central. 2. Follow IBM's upgrade documentation for Aspera Console. 3. Apply the update to all affected instances. 4. Restart the Aspera Console service.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict network access to Aspera Console to only trusted IP addresses and networks.

Web Application Firewall

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

🧯 If You Can't Patch

  • Implement strict network access controls to limit exposure
  • Deploy database monitoring and alerting for suspicious SQL queries

🔍 How to Verify

Check if Vulnerable:

Check the Aspera Console version via the web interface or configuration files. If version is between 3.4.0 and 3.4.2 inclusive, the system is vulnerable.

Check Version:

Check the version in the Aspera Console web interface under Admin > About, or examine the installation directory for version files.

Verify Fix Applied:

Verify the Aspera Console version is 3.4.3 or later after applying the patch.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL query patterns in database logs
  • Multiple failed login attempts followed by successful access
  • Unexpected database schema changes

Network Indicators:

  • Unusual SQL-like patterns in HTTP POST requests to Aspera Console endpoints
  • Outbound database connections from Aspera Console to unexpected destinations

SIEM Query:

source="aspera_console" AND (http_method="POST" AND (url="*sql*" OR body="*SELECT*" OR body="*UNION*" OR body="*DROP*" OR body="*INSERT*"))

🔗 References

📤 Share & Export