Corda Open Source 4.8 release notes
Corda Open Source 4.8 Apache Log4j update release notes (December 16 2021)
Corda 4.8 was updated on December 16th 2021 to fix the urgent security issue - CVE-2021-44228 - caused by the Apache Log4j 2 dependency.
To build the latest version of Corda 4.8:
- Open a terminal window in the directory where you want to download the Corda repository.
- Clone the Corda repository by running this command:
git clone https://github.com/corda/corda.git
- Checkout the release branch for Corda 4.8 by running this command:
git checkout origin/release/os/4.8
- Run the command:
node/capsule/build/libs/corda-4.8-SNAPSHOT.jar, this replaces your node’s current
corda.jar. To replace the superseded
.jarfile, follow the instructions on upgrading your node to Corda 4.8.
Corda Open Sourve 4.8 release notes
Corda 4.8, released on April 21st 2021, includes several fixes and improvements.
You can use states and CorDapps valid in Corda 3.0 and above with Corda 4.8.
For the commitment Corda makes to wire and API stability, see API stability guarantees.
Long-term support release
Corda 4.8 and Corda Enterprise Edition 4.8 are our long-term support (LTS) platform versions.
R3 provides LTS for this release for 30 months starting April 21st 2021. This is 6 months longer than the support periods for previous releases, giving Corda customers extra time to plan for the next upgrade.
Platform version change
Corda 4.8 uses platform version 10.
For more information about platform versions, see Versioning.
Corda 4.8 fixes:
- Transaction verification being performed outside of the attachments class loader.
- Inconsistencies in source code comments.
- Privileges escalation caused by flows disabling validation.
- Attachment presence cache containing the attachment contents.
- Permissions failing for
- Service loader leaking
- A security issue in a Corda dependency.
CordaPersistence.transactionfailing to flush correctly.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.