Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP XRP Ledger 修复严重整数溢出漏洞：未造成实际损失，供应上限依然稳固
10月9日，XRP Ledger（XRPL）开发者披露，网络支付引擎中存在一个整数溢出漏洞。该漏洞理论上允许攻击者凭空创造新的 XRP，从而打破2012年账本启动时设定的1000亿枚代币供应上限。
根据官方漏洞披露报告，该缺陷已在9月25日发布的 xrpld 3.4.1 软件版本中得到修补。RippleX 表示，目前未发现该漏洞在公共网络上被利用的证据。
该漏洞由研究员 Cayden Liao 和 Veria AI 于9月22日通过 XRPL 漏洞赏金计划报告。RippleX 工程师在独立服务器上成功复现了该攻击，确认新创建的 XRP 可在后续交易中被花费，并将该发现的严重程度从“重大”提升至“关键”。
漏洞如何“铸造”XRP？
该漏洞位于支付引擎的溢出处理机制中。当单笔支付消耗账本内置交易所中的大量挂单时，软件使用64位整数加法计算买方应付金额，且未进行溢出检查。
如果涉及数百个挂单，每个挂单要求的 XRP 数量极大，总和可能会超过64位整数所能容纳的最大值，导致数值回绕（wrap around）为一个极小的值。此时，每个挂单的持有者都能获得全额支付，而买方仅被扣除回绕后的微小金额，从而使得新“铸造”的 XRP 落入攻击者账户。
There were originally two security lines to prevent this behavior, but both failed:
- The ledger "no XRP generated" invariant: It calculates the change in net balance in the same way, so the same loop occurred, and no abnormalities were detected.
- Single account balance check: Failure will only be triggered if a single account holds XRP that exceeds the total supply. The attacker successfully avoided this check by spreading the newly minted XRP across hundreds of accounts.
Why did this fix skip the regular revision process?
Normally, changes to XRP Ledger's transaction processing rules require an "amendment" process: new rules must be dormant and have the support of more than 80% of trusted verification nodes within two weeks before they can take effect.
For the first time since it introduced the process more than ten years ago, RippleX decided to skip this step and directly release the fix. The reason is that the vulnerability is extremely low-cost to exploit, requires no special permissions, and can generate expendable XRP. Since xrpld is open source software, if normal procedures are followed, the repair code will be publicly visible on the main network for several weeks, but it may still be exploited.
Although this shortcut brings the risk of mixed version network stagnation, the risk is controllable because normal transactions cannot reach vulnerable code paths. On the day version 3.4.1 was released, more than 80% of the default UNL verification nodes were running that version and deployment was completed before the source code was publicly released.
Significance for XRP fixed supply
The incident highlights one of the core of XRP's value proposition: its supply must be provably limited. All 100 billion tokens were created at launch, and the institution built on the ledger views this cap as a hard guarantee.
Although the vulnerability has existed since the current payment engine was written in 2015, RippleX confirmed that it has never found any signs of being exploited.
The same version also fixed another bulk transaction wrapper verification flaw that was activated on the main network on October 9. RippleX said it will add a re-verification step to its release process to ensure that all security issues marked as "fixed" are retested during the release candidate phase.
As XRP Ledger continues to add institutional-level functions (including delegation of authority for banks and stablecoins), and XRP's supply and custody dynamics continue to attract holders 'attention, the proper handling of this security incident has further consolidated market confidence.
