CVE-2025-65998: Apache Syncope: Default AES key used for internal password encryption
Apache Syncope can be configured to store the user password values in the internal database with AES encryption, though this is not the default option.
When AES is configured, the default key value, hard-coded in the source code, is always used. This allows a malicious attacker, once obtained access to the internal database content, to reconstruct the original cleartext password values. This is not affecting encrypted plain attributes, whose values are also stored using AES encryption.
Users are recommended to upgrade to version 3.0.15 / 4.0.3, which fix this issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-65998?
The severity of CVE-2025-65998 is classified as high due to the exposure of user password values if AES encryption is improperly configured.
How do I fix CVE-2025-65998?
To fix CVE-2025-65998, ensure that AES encryption is not used with its default hard-coded key, and implement a custom key for encryption.
Which versions of Apache Syncope are affected by CVE-2025-65998?
CVE-2025-65998 affects Apache Syncope versions up to 3.0.15 and 4.0.3.
What is the impact of CVE-2025-65998?
The impact of CVE-2025-65998 includes potential unauthorized access to user passwords, which can lead to account compromise.
Is it safe to use AES encryption in Apache Syncope with default settings?
Using AES encryption with default settings in Apache Syncope is unsafe as it relies on a hard-coded key, making it vulnerable to attacks.