Описание
Janssen Config API returns results without scope verification
Impact
What kind of vulnerability is it? Who is impacted? The configAPI is an internal service and hence should never be exposed to the internet. With that said, this is a serious vulnerability that has a large internal surface attack area that exposes all sorts of information from the IDP including clients, users, scripts ..etc.
This affects all users of Janssen <1.8.0 and Gluu Flex <5.8.0
Patches
Has the problem been patched? What versions should users upgrade to? All users are advised to upgrade immediately to 1.8.0 for Janssen users and 5.8.0 For Flex users.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading? The user can potentially fork and build the config api and patch it in their system following the commit here https://github.com/JanssenProject/jans/commit/92eea4d4637f1cae16ad2f07b2c16378ff3fc5f1
References
Are there any links users can visit to find out more? https://github.com/JanssenProject/jans/issues/11575 https://github.com/JanssenProject/jans/commit/92eea4d4637f1cae16ad2f07b2c16378ff3fc5f1
Ссылки
- https://github.com/JanssenProject/jans/security/advisories/GHSA-373j-mhpf-84wg
- https://nvd.nist.gov/vuln/detail/CVE-2025-53003
- https://github.com/JanssenProject/jans/issues/11575
- https://github.com/JanssenProject/jans/commit/92eea4d4637f1cae16ad2f07b2c16378ff3fc5f1
- https://github.com/GluuFederation/flex/releases/tag/v5.8.0
- https://github.com/JanssenProject/jans/releases/tag/v1.8.0
Пакеты
io.jans:jans-config-api-server
< 1.8.0
1.8.0
Связанные уязвимости
The Janssen Project is an open-source identity and access management (IAM) platform. Prior to version 1.8.0, the Config API returns results without scope verification. This has a large internal surface attack area that exposes all sorts of information from the IDP including clients, users, scripts ..etc. This issue has been patched in version 1.8.0. A workaround for this vulnerability involves users forking and building the config api, patching it in their system following commit 92eea4d.