CVE-2023-42034

8.8 HIGH

📋 TL;DR

This vulnerability in Visualware MyConnection Server allows remote attackers to bypass authentication via cross-site scripting (XSS) in the doRTAAccessCTConfig method. Attackers can inject malicious scripts without proper authentication, potentially gaining unauthorized access. Organizations running affected MyConnection Server installations are at risk.

💻 Affected Systems

Products:
  • Visualware MyConnection Server
Versions: Specific versions not detailed in advisory; check vendor advisory for exact affected versions
Operating Systems: All platforms running MyConnection Server
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with the vulnerable doRTAAccessCTConfig method are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise where attackers gain administrative access, steal sensitive data, deploy ransomware, or pivot to other network systems.

🟠

Likely Case

Unauthorized access to MyConnection Server functionality, data exfiltration, or use as an initial foothold for further attacks.

🟢

If Mitigated

Limited impact with proper network segmentation, web application firewalls, and monitoring detecting exploitation attempts.

🌐 Internet-Facing: HIGH - Remote exploitation with minimal user interaction makes internet-facing instances particularly vulnerable.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this, but requires network access.

🎯 Exploit Status

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

ZDI-CAN-21613 indicates proof-of-concept exists in controlled disclosure. Minimal interaction required for exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched version

Vendor Advisory: https://myconnectionserver.visualware.com/support/security-advisories

Restart Required: Yes

Instructions:

1. Review vendor security advisory. 2. Download latest patched version. 3. Backup configuration and data. 4. Install update following vendor instructions. 5. Restart MyConnection Server services. 6. Verify functionality.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy WAF with XSS protection rules to block exploitation attempts

Network Segmentation

all

Restrict access to MyConnection Server to trusted networks only

🧯 If You Can't Patch

  • Isolate MyConnection Server behind firewall with strict access controls
  • Implement strong monitoring and alerting for authentication bypass attempts

🔍 How to Verify

Check if Vulnerable:

Check MyConnection Server version against vendor advisory. Test for XSS vulnerabilities in doRTAAccessCTConfig endpoint.

Check Version:

Check MyConnection Server web interface or configuration files for version information

Verify Fix Applied:

Verify updated version matches patched version from vendor advisory. Test that authentication bypass via XSS is no longer possible.

📡 Detection & Monitoring

Log Indicators:

  • Unusual authentication patterns
  • Access to doRTAAccessCTConfig with script-like parameters
  • Failed authentication followed by successful access

Network Indicators:

  • HTTP requests to doRTAAccessCTConfig with script injection patterns
  • Unexpected administrative access from new IP addresses

SIEM Query:

source="myconnection_server" AND (uri="*doRTAAccessCTConfig*" AND (param="*<script>*" OR param="*javascript:*"))

🔗 References

📤 Share & Export