CVE-2024-2321 — am-parent
MEDIUMCVE-2024-2321 is a medium-severity (CVSS 5.6) CWE-863 vulnerability in org.wso2.am:am-parent. No vendor fix is recorded yet; mitigation options are listed below.
WSO2 incorrect authorization vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-2321.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-2321 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.wso2.am:am-parent☕org.wso2.am:am-parent☕org.wso2.am:am-parent☕org.wso2.is:identity-server-parent☕org.wso2.is:identity-server-parent☕org.wso2.is:identity-server-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An incorrect authorization vulnerability exists in multiple WSO2 products, allowing protected APIs to be accessed directly using a refresh token instead of the expected access token. Due to improper authorization checks and token mapping, session cookies are not required for API access, potentially enabling unauthorized operations.
Exploitation requires an attacker to obtain a valid refresh token of an admin user. Since refresh tokens generally have a longer expiration time, this could lead to prolonged unauthorized access to API resources, impacting data confidentiality and integrity.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wso2.am:am-parent | ≥ 4.2.0-beta | No fix |
| ☕Maven | org.wso2.am:am-parent | ≥ 4.1.0-alpha | No fix |
| ☕Maven | org.wso2.am:am-parent | ≥ 4.0.0-beta | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 6.1.0-beta | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 6.0.0-alpha3 | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 5.11.0-alpha | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.am:am-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.wso2.am:am-parent has shipped for CVE-2024-2321 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-2321 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-2321. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-2321 in your dependencies?
O3 Security finds CVE-2024-2321 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.