CVE-2021-41744

9.8 CRITICAL

📋 TL;DR

CVE-2021-41744 is a critical command injection vulnerability in Yongyou PLM software that allows unauthenticated attackers to execute arbitrary commands on affected servers. All versions of Yongyou PLM are affected, putting organizations using this product lifecycle management system at risk. Attackers can exploit this to gain full server control through the default JBoss management interface.

💻 Affected Systems

Products:
  • Yongyou PLM
  • UFIDA PLM
Versions: All versions
Operating Systems: Any OS running Yongyou PLM with JBoss
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the default JBoss configuration used by Yongyou PLM, allowing unauthorized access to management control background.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise leading to data theft, ransomware deployment, lateral movement within the network, and persistent backdoor installation.

🟠

Likely Case

Unauthenticated remote code execution allowing attackers to steal sensitive product data, intellectual property, and customer information from the PLM system.

🟢

If Mitigated

Limited impact if network segmentation isolates PLM systems and strict access controls prevent external exploitation.

🌐 Internet-Facing: HIGH - Default configuration exposes management interface without authentication, making internet-facing systems immediately vulnerable.
🏢 Internal Only: HIGH - Even internally, the vulnerability allows any network user to compromise the PLM server without credentials.

🎯 Exploit Status

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

The vulnerability requires no authentication and has public proof-of-concept available, making exploitation trivial for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.cnvd.org.cn/flaw/show/CNVD-2021-39097

Restart Required: Yes

Instructions:

1. Contact Yongyou/UFIDA for official patches or updates. 2. Apply any available security updates. 3. Restart the PLM service and JBoss application server. 4. Verify the management interface requires authentication.

🔧 Temporary Workarounds

Disable Unauthenticated JBoss Management

all

Configure JBoss to require authentication for management interfaces

Edit JBoss configuration files to enable authentication
Set security constraints in web.xml and jboss-web.xml

Network Access Control

linux

Restrict access to JBoss management ports (default 8080, 9990)

iptables -A INPUT -p tcp --dport 8080 -s TRUSTED_IP -j ACCEPT
iptables -A INPUT -p tcp --dport 9990 -s TRUSTED_IP -j ACCEPT
iptables -A INPUT -p tcp --dport 8080 -j DROP
iptables -A INPUT -p tcp --dport 9990 -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate PLM systems from untrusted networks
  • Deploy web application firewall (WAF) with command injection protection rules

🔍 How to Verify

Check if Vulnerable:

Attempt to access JBoss management console without authentication at http://[server]:8080/ or http://[server]:9990/. If accessible, system is vulnerable.

Check Version:

Check PLM version through application interface or consult vendor documentation for version identification.

Verify Fix Applied:

Verify that JBoss management interfaces now require authentication and return 401/403 for unauthenticated access attempts.

📡 Detection & Monitoring

Log Indicators:

  • Unauthenticated access to /console/ or /management paths in JBoss logs
  • Command execution patterns in system logs
  • Unusual process creation from JBoss/JVM

Network Indicators:

  • Unusual outbound connections from PLM server
  • Command and control traffic patterns
  • Exploit kit signatures targeting JBoss

SIEM Query:

source="jboss.log" AND (url="/console/*" OR url="/management/*") AND status="200" AND user="-"

🔗 References

📤 Share & Export