CVE-2025-45613

7.5 HIGH

📋 TL;DR

This vulnerability in Shiro-Action v0.6 allows attackers to bypass access controls on the /user/list endpoint, potentially exposing sensitive user information. Any system running the vulnerable version is affected, particularly those with internet-facing deployments. The flaw stems from improper authorization checks in the application component.

💻 Affected Systems

Products:
  • Shiro-Action
Versions: v0.6
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with the /user/list endpoint enabled and accessible. The vulnerability is in the application layer, not OS-dependent.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could exfiltrate all user data including potentially sensitive personal information, credentials, or system metadata, leading to data breaches and credential theft.

🟠

Likely Case

Unauthorized access to user lists containing usernames, email addresses, and potentially other profile information that could be used for targeted attacks.

🟢

If Mitigated

With proper network segmentation and access controls, impact would be limited to the specific application instance with no lateral movement.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The GitHub issue shows exploitation details. Attack requires crafting specific payloads to bypass access controls.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: https://github.com/zhaojun1998/Shiro-Action/issues/24

Restart Required: Yes

Instructions:

1. Monitor the GitHub repository for updates. 2. Apply any future patches from the maintainer. 3. Restart the application after patching.

🔧 Temporary Workarounds

Disable /user/list endpoint

all

Remove or restrict access to the vulnerable endpoint

# Modify application configuration to disable /user/list route
# Add access control rules to block /user/list requests

Implement WAF rules

all

Block requests to /user/list endpoint at network level

# Example nginx rule: location /user/list { deny all; }
# Example Apache rule: <Location /user/list> Require all denied </Location>

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the application
  • Deploy web application firewall with rules to block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Test if unauthenticated requests to /user/list endpoint return user data. Use curl: curl -X GET http://target/user/list

Check Version:

Check application configuration or package manager for Shiro-Action version

Verify Fix Applied:

Verify that unauthorized requests to /user/list return proper access denied responses (401/403) instead of user data

📡 Detection & Monitoring

Log Indicators:

  • Multiple unauthorized requests to /user/list endpoint
  • Unusual access patterns to user data endpoints
  • Requests with crafted payloads in URL parameters

Network Indicators:

  • HTTP GET requests to /user/list from untrusted sources
  • Unusual data exfiltration patterns from application server

SIEM Query:

source="web_server" AND (url_path="/user/list" AND (response_code=200 OR response_size>threshold))

🔗 References

📤 Share & Export