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.β¦