Apache Syncope: Use of Hard-coded Cryptographic Key
CVE-2025-65998 is a high-severity use of hard-coded cryptographic key vulnerability in Apache Syncope from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Apache Syncope versions: 2.1 through 2.1.14; 3.0 through 3.0.14; 4.0 through 4.0.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.53% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Syncope to 3.0.15 or 4.0.3, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Syncope | 2.1 through 2.1.14; 3.0 through 3.0.14; 4.0 through 4.0.2 | Not stated |
| Apache | Syncope | 2.1.0 through 2.1.14; 3.0.0 up to, but not including, 3.0.15; 4.0.0 up to, but not including, 4.0.3 | 3.0.15, 4.0.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Cryptographic Key
The product uses a hard-coded, unchangeable cryptographic key.
How developers prevent this class of flaw
- Prevention schemes mirror that of hard-coded password storage.
More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- openwall.com/lists/oss-security/2025/11/24/1Mailing List, Third Party Advisory
Other vulnerabilities in Apache Syncope
- 9.8 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Use of Hard-coded Cryptographic Key vulnerabilities
- 8.1 High severity
- 9.1 Critical severity
- 7.7 High severity
- 7.0 High severity
- 8.1 High severity
- 9.8 Critical severity
Spotted an error? Tell us.