CVE-2022-30354

7.5 HIGH

📋 TL;DR

OvalEdge versions 5.2.8.0 and earlier expose sensitive user ID data through an authenticated GET request to /user/getUserWithTeam. This vulnerability allows authenticated attackers to enumerate all registered user IDs, potentially facilitating further attacks. Organizations running affected OvalEdge versions are impacted.

💻 Affected Systems

Products:
  • OvalEdge
Versions: 5.2.8.0 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authentication but affects all authenticated users regardless of privilege level.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers combine user ID enumeration with other vulnerabilities to compromise accounts, escalate privileges, or conduct targeted attacks against specific users.

🟠

Likely Case

Authenticated users (including low-privileged ones) can enumerate all user IDs, enabling reconnaissance for credential attacks, social engineering, or privilege escalation attempts.

🟢

If Mitigated

With proper access controls and network segmentation, impact is limited to authorized users accessing data they shouldn't see, still violating privacy principles.

🌐 Internet-Facing: HIGH if OvalEdge is internet-facing, as authenticated attackers could exploit this from anywhere.
🏢 Internal Only: MEDIUM as it requires authentication but could be exploited by malicious insiders or compromised internal accounts.

🎯 Exploit Status

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

Simple HTTP GET request to vulnerable endpoint with valid authentication. Public references demonstrate exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 5.2.8.0

Vendor Advisory: https://cve.offsecguy.com/ovaledge/vulnerabilities/sensitive-data-exposure#cve-2022-30354

Restart Required: Yes

Instructions:

1. Upgrade to OvalEdge version newer than 5.2.8.0. 2. Apply vendor-provided patches. 3. Restart OvalEdge services. 4. Verify the endpoint no longer exposes sensitive data.

🔧 Temporary Workarounds

Web Application Firewall Rule

all

Block or monitor requests to /user/getUserWithTeam endpoint

WAF-specific configuration required

Access Control Restriction

all

Restrict access to vulnerable endpoint to only necessary administrative users

Application-specific access control configuration

🧯 If You Can't Patch

  • Implement strict network segmentation to limit OvalEdge access to authorized users only
  • Monitor and alert on requests to /user/getUserWithTeam endpoint in application logs

🔍 How to Verify

Check if Vulnerable:

As authenticated user, send GET request to /user/getUserWithTeam endpoint. If it returns user ID data, system is vulnerable.

Check Version:

Check OvalEdge admin interface or configuration files for version information

Verify Fix Applied:

After patching, same request should return error or no sensitive data. Verify endpoint behavior changed.

📡 Detection & Monitoring

Log Indicators:

  • HTTP GET requests to /user/getUserWithTeam
  • Unusual volume of requests to user endpoints

Network Indicators:

  • GET /user/getUserWithTeam HTTP/1.1 in web traffic

SIEM Query:

source="ovaledge" AND uri_path="/user/getUserWithTeam" AND http_method="GET"

🔗 References

📤 Share & Export