CVE-2024-25812

6.1 MEDIUM

📋 TL;DR

MyNET up to version 26.05 contains a reflected cross-site scripting (XSS) vulnerability in the src parameter. This allows attackers to inject malicious scripts that execute in users' browsers when they visit a crafted URL. Organizations using vulnerable MyNET versions are affected.

💻 Affected Systems

Products:
  • MyNET
Versions: Up to and including v26.05
Operating Systems: All supported OS
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using the vulnerable src parameter are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, perform actions on behalf of authenticated users, or deliver malware.

🟠

Likely Case

Session hijacking leading to unauthorized access, credential theft, or defacement of web pages.

🟢

If Mitigated

Limited impact if input validation and output encoding are properly implemented, though some risk remains.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Reflected XSS vulnerabilities are commonly exploited with simple payloads; exploitation requires user interaction with a malicious link.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: v26.06 or later

Vendor Advisory: https://www.airc.pt/solucoes-servicos/solucoes?segment=MYN

Restart Required: Yes

Instructions:

1. Download the latest MyNET version from the official vendor site. 2. Backup current configuration and data. 3. Install the update following vendor instructions. 4. Restart the MyNET service.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side validation to sanitize the src parameter by removing or encoding special characters.

Implement regex filter: /^[a-zA-Z0-9\-\.\/]+$/ for src parameter

Web Application Firewall (WAF)

all

Deploy a WAF with XSS protection rules to block malicious requests containing script tags or JavaScript.

Enable XSS protection rules in WAF configuration

🧯 If You Can't Patch

  • Implement Content Security Policy (CSP) headers to restrict script execution sources.
  • Disable or restrict access to the vulnerable endpoint if not essential for operations.

🔍 How to Verify

Check if Vulnerable:

Test by injecting a simple XSS payload like <script>alert('XSS')</script> into the src parameter and check if it executes in the browser.

Check Version:

Check MyNET version via admin interface or configuration file; command varies by installation.

Verify Fix Applied:

After patching, retest with the same XSS payload; it should be sanitized or blocked without execution.

📡 Detection & Monitoring

Log Indicators:

  • Log entries showing src parameter with script tags or JavaScript code
  • Unusual requests to the vulnerable endpoint

Network Indicators:

  • HTTP requests with src parameter containing suspicious strings like <script> or javascript:

SIEM Query:

source="mynet_logs" AND (src="*<script>*" OR src="*javascript:*")

🔗 References

📤 Share & Export