AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 65 Bitcoin

daemon: set restrictive permission on RPC-server unix domain socket

Public commit record

What the developer wrote

Authored by SomberNight

50/100 · Thin
daemon: set restrictive permission on RPC-server unix domain socket

0600 instead of 0775.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

Electrum's background daemon runs a local control server using a Unix domain socket. Previously, that socket file was created with permissions 0775, meaning any user in the same group could connect to it and potentially control the wallet. This commit changes the permissions to 0600, so only the wallet's owner can access the socket. The commit itself notes a possible race condition: for a brief moment after the socket is created and before the permissions are tightened, other users might still be able to connect.

Recommended action

Apply the patch. For defense in depth, consider running the daemon with a umask that denies group/other access by default, or use a more controlled socket-creation path that avoids the race window noted in the FIXME comment.

Security signals we found

01

permission tightening on local RPC socket

02

acknowledged race condition between socket creation and chmod

03

local privilege boundary issue (group-writable socket)

04

no CVE or advisory referenced in commit

Risk score

Why this scored 65/100

Our methodology →
Potential impact 18/30
Exploitability 15/25
Stealth signal 10/15
Affected reach 10/15
Confidence 8/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.