CVE-2023-51063

8.8 HIGH

📋 TL;DR

This vulnerability allows attackers to inject malicious scripts into the QStar Archive Solutions web interface via the qnme-ajax?method=tree_level component. When exploited, it can lead to session hijacking, credential theft, or redirection to malicious sites. Organizations using QStar Archive Solutions Release RELEASE_3-0 Build 7 Patch 0 are affected.

💻 Affected Systems

Products:
  • QStar Archive Solutions
Versions: Release RELEASE_3-0 Build 7 Patch 0
Operating Systems: All supported OS
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the web interface component; any system with this version exposed to user input is vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of user sessions, administrative account takeover, data exfiltration, and lateral movement within the network.

🟠

Likely Case

Session hijacking leading to unauthorized access to archived data, credential theft from authenticated users, and potential malware delivery.

🟢

If Mitigated

Limited impact with proper input validation, output encoding, and Content Security Policy (CSP) headers in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

DOM-based reflected XSS typically requires user interaction (clicking a malicious link) but can be exploited without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor for updated release

Vendor Advisory: https://github.com/Oracle-Security/CVEs/blob/main/QStar%20Archive%20Solutions/CVE-2023-51063.md

Restart Required: Yes

Instructions:

1. Contact QStar support for patch availability. 2. Apply the official patch. 3. Restart the QStar Archive Solutions service. 4. Verify the fix by testing the vulnerable endpoint.

🔧 Temporary Workarounds

Implement Content Security Policy (CSP)

all

Add CSP headers to restrict script execution sources.

Add 'Content-Security-Policy: script-src 'self'' to web server headers

Input Validation and Output Encoding

all

Sanitize user input in the qnme-ajax endpoint.

Implement proper input validation and HTML encoding in the application code

🧯 If You Can't Patch

  • Restrict network access to the QStar web interface using firewall rules.
  • Implement a Web Application Firewall (WAF) with XSS protection rules.

🔍 How to Verify

Check if Vulnerable:

Test the qnme-ajax?method=tree_level endpoint with XSS payloads like <script>alert('XSS')</script> and check if script executes.

Check Version:

Check the QStar Archive Solutions version in the admin interface or configuration files.

Verify Fix Applied:

Retest the endpoint with XSS payloads after patching; scripts should not execute and input should be properly encoded.

📡 Detection & Monitoring

Log Indicators:

  • Unusual requests to qnme-ajax?method=tree_level with script tags or encoded payloads
  • Multiple failed login attempts following suspicious requests

Network Indicators:

  • HTTP requests containing script tags or JavaScript code in query parameters
  • Traffic patterns indicating redirection to external domains

SIEM Query:

source="qstar_logs" AND uri="*qnme-ajax*" AND (query="*<script>*" OR query="*javascript:*")

🔗 References

📤 Share & Export