CVE-2025-65998

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.

CVSS v3 7.5 HIGH

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://lists.apache.org/thread/fjh0tb0d1xkbphc5ogdsc348ppz88cts	Mailing List Vendor Advisory
http://www.openwall.com/lists/oss-security/2025/11/24/1	Mailing List Third Party Advisory

Configurations

Configuration 1 (hide)

OR	cpe:2.3:a:apache:syncope::::::::
	cpe:2.3:a:apache:syncope::::::::
	cpe:2.3:a:apache:syncope::::::::

History

No history.

Information

Published : 2025-11-24 14:15

Updated : 2025-11-26 14:30

NVD link : CVE-2025-65998

Mitre link : CVE-2025-65998

CVE.ORG link : CVE-2025-65998

JSON object : View

Products Affected

apache

syncope

CWE

CWE-321

Use of Hard-coded Cryptographic Key

{"id": "CVE-2025-65998", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2025-11-24T14:15:48.417", "references": [{"url": "https://lists.apache.org/thread/fjh0tb0d1xkbphc5ogdsc348ppz88cts", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2025/11/24/1", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-321"}]}], "descriptions": [{"lang": "en", "value": "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.\n\nWhen 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.\nThis is not affecting encrypted plain attributes, whose values are also stored using AES encryption.\n\nUsers are recommended to upgrade to version 3.0.15 / 4.0.3, which fix this issue."}], "lastModified": "2025-11-26T14:30:26.730", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:syncope:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D773E581-822F-4431-BEFB-48BE61A743EC", "versionEndIncluding": "2.1.14", "versionStartIncluding": "2.1.0"}, {"criteria": "cpe:2.3:a:apache:syncope:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "DE40E959-C93C-43E0-80AE-4FAB31C47165", "versionEndExcluding": "3.0.15", "versionStartIncluding": "3.0.0"}, {"criteria": "cpe:2.3:a:apache:syncope:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "EFD9390D-0F3F-453D-ACCC-BFF74C6D9623", "versionEndExcluding": "4.0.3", "versionStartIncluding": "4.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}