CVE-2025-22173

4.3 MEDIUM

📋 TL;DR

Jira Align has an authorization vulnerability where low-privilege users can access endpoints they shouldn't, potentially viewing sensitive sprint data. This affects all Jira Align instances with users who have limited permissions. The vulnerability allows unauthorized access to restricted information.

💻 Affected Systems

Products:
  • Atlassian Jira Align
Versions: Specific versions not specified in CVE, but likely multiple recent versions
Operating Systems: All platforms running Jira Align
Default Config Vulnerable: ⚠️ Yes
Notes: Affects standard Jira Align deployments with role-based access control. The vulnerability exists in the authorization logic.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Low-privilege users could access sensitive business data, intellectual property, or internal planning information that should be restricted to higher-level roles.

🟠

Likely Case

Users with basic access can view sprint data, team metrics, or project details they shouldn't have permission to see, potentially exposing internal planning information.

🟢

If Mitigated

With proper access controls and monitoring, impact is limited to minor information disclosure with no data modification capabilities.

🌐 Internet-Facing: MEDIUM - If Jira Align is exposed to the internet, unauthorized users could potentially access sensitive information, though authentication is still required.
🏢 Internal Only: MEDIUM - Internal users with low privileges could access restricted sprint data and planning information they shouldn't see.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires authenticated access with any user account. Attackers need to discover and access specific endpoints that bypass authorization checks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Atlassian advisory for specific fixed versions

Vendor Advisory: https://jira.atlassian.com/browse/JIRAALIGN-8642

Restart Required: No

Instructions:

1. Review Atlassian advisory JIRAALIGN-8642. 2. Update Jira Align to the latest patched version. 3. Verify authorization controls are working correctly post-update.

🔧 Temporary Workarounds

Tighten Access Controls

all

Review and restrict user permissions to minimum necessary access. Implement additional authorization checks at the application level.

Network Segmentation

all

Restrict access to Jira Align to only authorized users and networks. Implement IP whitelisting if possible.

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the Jira Align instance
  • Enable detailed logging and monitoring for unauthorized access attempts to sensitive endpoints

🔍 How to Verify

Check if Vulnerable:

Test with low-privilege user accounts attempting to access sprint data endpoints that should be restricted to higher roles.

Check Version:

Check Jira Align administration panel or consult Atlassian documentation for version information

Verify Fix Applied:

After patching, retest with low-privilege users to ensure they cannot access restricted sprint data endpoints.

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns from low-privilege users to sprint-related endpoints
  • Failed authorization attempts followed by successful access

Network Indicators:

  • HTTP requests to sprint data endpoints from unauthorized user accounts

SIEM Query:

source="jira-align" AND (endpoint="*/sprint*" OR endpoint="*/planning*") AND user_role="low_privilege" AND response_code=200

🔗 References

📤 Share & Export