AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 45 Cryptographic libraries

rpc: restrict get_alt_blocks_hashes

Public commit record

What the developer wrote

Authored by selsta

35/100 · Opaque
rpc: restrict get_alt_blocks_hashes
✓ Descriptive subject! No meaningful explanatory body
The short version

What changed, and why it matters

This commit changes one line in Monero's RPC server so that the get_alt_blocks_hashes endpoint is no longer available when the node is running in restricted mode. Previously, any caller could ask a restricted node for the list of alternative (orphaned/uncles) block hashes. The change suggests the developers decided this information should be treated as privileged, but the commit message does not explain why.

Recommended action

Treat as a minor hardening change. If running a public/restricted Monero RPC node, ensure this patch is applied so alternative-block hashes are not exposed to unauthenticated/unprivileged callers. Review whether other RPC endpoints expose similar metadata that should also be restricted.

Security signals we found

01

Access-control tightening on an RPC endpoint

02

Endpoint made conditional on !m_restricted

03

No explicit security explanation in commit message

04

No changes to handler logic or output sanitization

Risk score

Why this scored 45/100

Our methodology →
Potential impact 8/30
Exploitability 7/25
Stealth signal 10/15
Affected reach 9/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.