CVE-2013-4425 json
The DICOM listener in OsiriX before 5.8 and before 2.5-MD, when starting up, encrypts the TLS private key file using "SuperSecretPassword"…
published 12y ago modified 4mo ago also EUVD-2013-4302
- cvss
- 1.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
The DICOM listener in OsiriX before 5.8 and before 2.5-MD, when starting up, encrypts the TLS private key file using "SuperSecretPassword" as the hardcoded password, which allows local users to obtain the private key.
Is CVE-2013-4425 in your stack? 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
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
osvdb.org
/99518
vdb-entry
-
archives.neohapsis.com
/archives/bugtraq/2013-11/0029.html
mailing-list
-
securityfocus.com
/bid/63566
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/88606
vdb-entry
Sources
- CVE List CVE-2013-4425
- NVD CVE-2013-4425
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.