A vulnerability has been discovered in the XRP ledger that could generate XRP

核心要点

支付溢出漏洞可能导致产生可花费的XRP。XRPL（XRP Ledger）未发现该缺陷被利用的证据。修复补丁已于9月25日随xrpld 3.4.1版本发布。开发者绕过正常的修正案时间表，以更快关闭这一风险。

支付计算可能凭空产生XRP

XRPL于10月9日发布的漏洞报告描述了分类账支付引擎中存在的一个整数溢出缺陷。在精心构造的条件下，消耗大量订单簿报价的交易可能会向账户 credited（贷记）XRP，而发送方实际上并未支付这些金额。

交易中的每个报价单独看似乎都是有效的。问题出在引擎将所有报价的XRP金额相加时。一旦总额超过用于该计算的数字的最大大小，它可能会回绕到一个较小的值，而不是产生错误。

引擎仍会向报价所有者全额贷记其XRP金额，同时仅向买方收取回绕后的总金额。差额代表新创建的XRP，随后可以像其他余额一样移动、交易或发送到交易所。

为何该缺陷严重

攻击者无需拥有大量的XRP余额。攻击者可以控制放置报价的账户，支付账户储备金和交易费，然后将创建的XRP分散到这些账户中。

Account keys are not affected. The vulnerability lies in payment arithmetic logic rather than wallet access. Triggering it requires hundreds of deliberately priced quotes and a transaction designed to collectively consume those quotes; ordinary XRP payments or transactions will not reach the numerical level needed to create an overflow.

XRPL said it found no evidence of exploitation of the vulnerability on public networks, nor did it report private key leaks, financial losses, or consensus failures. This flaw has existed since the current payment engine was written in 2015, and has not been discovered since normal activity has never touched the arithmetic limit.

Existing safeguards against newly created XRPs also rely on the same type of addition operation. It may also occur in the same way as payment engines, making the transaction appear normal rather than marking an unexpected increase in the balance.

Why developers resorted to emergency deployment

Developers released overflow fixes before releasing technical details because normal amendment schedules would leave known exploitable vulnerabilities open for weeks. The patch was released on September 25 with xrpld version 3.4.1, and public disclosure took place on October 9.

XRPL usually changes trading rules through "amendments." The verification node first upgrades its software and then maintains support for a specified period of time before the new rules are activated simultaneously at all ledger points on the network. This process avoids situations where different servers reach different conclusions on the same transaction.

等待该过程在此处会造成困难。由于xrpld是开源软件，公布修复程序可能会让攻击者在旧软件仍接受易受攻击的交易路径时寻找目标。因此，团队决定让新的溢出检查在单个服务器升级时生效。

这种更快的方法带来了暂时的兼容性风险：未打补丁的服务器可能会接受已被升级服务器拒绝的 exploit 交易。开发人员认为，这比允许新创建的XRP进入市场更为安全。报告指出，在3.4.1版本发布当天，默认UNL（可信节点列表）上超过80%的验证节点已完成升级。

XRPL披露了第二个独立的缺陷

报告还详细说明了XRPL即将推出的Batch（批量）功能中的一个验证问题。该功能允许用户将多个交易作为一个单元提交。它可能导致运行不同版本软件的服务器就格式错误的Batch交易产生分歧，从而中断分类账验证或破坏解析交易数据的应用程序。

Batch flaws were discovered before the feature was launched on the main network. The overflow issue affects existing payment engine code, so its patch cannot wait for the standard activation cycle.

When the report was released, XRPL was activating a new account control tool for businesses. These changes involve different parts of the ledger, but all rely on node operators, wallet providers and developers to follow the same latest rules.

What users and operators need to do

Ordinary XRP holders do not need to transfer funds, change wallets, or exchange tokens. The update involves software that verifies transactions, rather than changes to user account balances, wallet keys or the amount of XRP supplies held.

• XRP Holders: No action is required.
• Exchange Users: If an exchange maintains its own XRPL infrastructure, please follow the platform notification.
• Node operators: Upgrade to xrpld 3.4.1 or later to stay in sync with the network.

With the activation of Batch fixes, old servers are now blocked by the fixes, which means they must be updated to continue to follow current ledger rules.

fix to protecting XRP before supply rules are tested

The disclosure demonstrated how close the ledger was to a supply integrity failure and why the verification node acted quickly. The flaw was fixed before the details were made public, no exploitation was found, and the payment engine now uses a check mechanism designed to prevent arithmetic errors before they reach the verified ledger.

This article is for reference only and does not constitute investment or technical advice. Node operators should review the latest XRPL release documents before updating their production infrastructure.