CVE-2014-3503 json
Apache Syncope uses a weak PNRG
published 12y ago modified 4mo ago also GHSA-4c72-mrhf-23cg , EUVD-2022-2354
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.0%
- EPSS 6.0% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.
Patch / fix
Is CVE-2014-3503 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
6.02% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.syncope:syncope | >=1.1.0, <1.1.8 |
1.1.8 |
Classification
References
-
github.com
/apache/syncope/commit/8e0045925a387ee211832c7e0709dd418cda1ad3
web
-
syncope.apache.org
/security.html
vendor-advisory
-
securityfocus.com
/archive/1/532669/100/0/threaded
mailing-list
-
packetstormsecurity.com
/files/127375/Apache-Syncope-Insecure-Password-Generation.html
web
-
securityfocus.com
/bid/68431
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2014-3503
advisory
-
syncope.apache.org
/security.html#cve-2014-3503-insecure-random-implementations-used-to-generate-p
web
-
web.archive.org
/web/20140728093808/http://www.securityfocus.com/bid/68431
web
-
web.archive.org
/web/20201207014021/http://www.securityfocus.com/archive/1/532669/100/0/threaded
web
-
svn.apache.org
/viewvc?view=revision&revision=r1596537
web
Sources
- CVE List CVE-2014-3503
- GitHub Advisory GHSA-4c72-mrhf-23cg
- NVD CVE-2014-3503
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.