CVE-2019-25057 json
In Corda before 4.1, the meaning of serialized data can be modified via an attacker-controlled CustomSerializer.
published 4y ago modified 4mo ago also EUVD-2019-11504
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
In Corda before 4.1, the meaning of serialized data can be modified via an attacker-controlled CustomSerializer.
Patch / fix
- r3 corda 4.1
Is CVE-2019-25057 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.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
References
-
docs.r3.com
/en/platform/corda/4.1/open-source/release-notes.html
release-notes, vendor-advisory
Sources
- CVE List CVE-2019-25057
- NVD CVE-2019-25057
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.