This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →
Q1What is this vulnerability? (Essence + Consequences)
🚨 **Essence**: Unauthenticated Information Disclosure in Atlassian Jira. <br>📉 **Consequences**: Attackers can **enumerate valid usernames** via the `/ViewUserHover.jspa` endpoint.…
🛡️ **Root Cause**: Improper access control on the `/ViewUserHover.jspa` endpoint. <br>🔍 **Flaw**: The system fails to restrict unauthenticated access to user hover data, allowing **username enumeration**.…
🏢 **Vendor**: Atlassian. <br>📦 **Product**: Jira Server & Data Center. <br>📅 **Affected Versions**: <br>- < 7.13.16 <br>- 8.0.0 ≤ v < 8.5.7 <br>- 8.6.0 ≤ v < 8.12.0 <br>✅ **Fixed**: 7.13.16, 8.5.7, 8.12.0+.
Q4What can hackers do? (Privileges/Data)
🕵️ **Attacker Actions**: <br>1. **Enumerate Users**: Validate if specific usernames exist. <br>2. **Data Leak**: Access sensitive user info via hover endpoints. <br>3.…
📉 **Threshold: LOW**. <br>🔑 **Auth**: **None required**. <br>⚙️ **Config**: Standard installation. <br>💡 Any internet-facing Jira instance with these versions is vulnerable. Easy to exploit with simple HTTP requests.
🔍 **Self-Check Methods**: <br>1. **Manual**: Send GET request to `/secure/ViewUserHover.jspa?userName=<target>`. Check response for user data vs. error. <br>2.…