NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2024-2321 — am-parent

MEDIUM

CVE-2024-2321 is a medium-severity (CVSS 5.6) CWE-863 vulnerability in org.wso2.am:am-parent. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

WSO2 incorrect authorization vulnerability

Also known asGHSA-6qjp-wm6g-m32r
Published
Updated
Affected
6 pkgs
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk
0.00%0.25%0.49%0.74%0.2%0.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected
☕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-parent

Real-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

6 total
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wso2.am:am-parent≥ 4.2.0-betaNo fix
☕Mavenorg.wso2.am:am-parent≥ 4.1.0-alphaNo fix
☕Mavenorg.wso2.am:am-parent≥ 4.0.0-betaNo fix
☕Mavenorg.wso2.is:identity-server-parent≥ 6.1.0-betaNo fix
☕Mavenorg.wso2.is:identity-server-parent≥ 6.0.0-alpha3No fix
☕Mavenorg.wso2.is:identity-server-parent≥ 5.11.0-alphaNo fix

Affected Products

2 products · 6 configurations
Application
api managerwso2
3 versions
4.0.04.1.04.2.0
Application
identity serverwso2
3 versions
5.11.06.0.06.1.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Remediation status

    The records we use list no patched version of org.wso2.am:am-parent for CVE-2024-2321. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-2321 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-2321: am-parent (Medium 5.6)