ME News reports that on October 10 (UTC+8), Ripple released a vulnerability disclosure report for XRP Ledger version 3.4.1, covering two issues. The XRP payment engine overflow has been rated as critical and affects versions 3.4.0 and earlier: the payment engine uses a 64-bit integer to aggregate amounts across multiple orders without overflow checks; when the sum exceeds the upper limit, it wraps around, crediting the full amount to the order provider while only charging the buyer the wrapped amount, thereby minting spendable XRP out of thin air. Exploitation requires constructing hundreds of malicious orders, costing approximately hundreds of XRP in reserve and fees, and cannot be triggered by normal payments. The report states there is no evidence this vulnerability has been exploited on any public network. The internal transaction encapsulation validation (fixBatchV1_2) is listed as a pre-activation blocker, affecting versions 3.3.0 and 3.4.0: the XLS-56 batch feature requires internal transactions to be encapsulated within the RawTransaction field, but servers did not enforce this requirement; objects without template-defined fields could serve as encapsulation, while fields from existing templates were rejected, potentially causing consensus divergence among nodes with differing version definitions. Activating BatchV1_1 without this fix risks network liveness disruption or malformed ledger entries. This issue has been resolved by the fixBatchV1_2 amendment in version 3.4.1, which was activated on the mainnet on October 9. The report confirms no funds were lost or private keys compromised due to this issue. The payment engine overflow fix became effective immediately with the release of version 3.4.1 on September 25 and did not require an amendment process. The payment engine vulnerability was reported and accompanied by a proof-of-concept via the bug bounty program by Cayden Liao and Veria AI. (Source: Foresight News)
Ripple Discloses Two Vulnerabilities in xrpld 3.4.1
KuCoinFlashShare
Summary
On October 10 (UTC+8), Ripple disclosed two vulnerabilities in xrpld 3.4.1, including a severe integer overflow in the payment engine affecting versions 3.4.0 and earlier. This flaw could allow attackers to mint XRP by exploiting overflow in order amounts. A pre-activation blocker in fixBatchV1_2 also introduced consensus risks in versions 3.3.0 and 3.4.0. Both issues have been resolved in the latest release. This update underscores the critical importance of addressing smart contract vulnerabilities in Layer 1 blockchain infrastructure.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.