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

feat: add wasm manifest (#4089)

Public commit record

What the developer wrote

Authored by Vlad Stan

65/100 · Adequate
feat: add wasm manifest (#4089)

Co-authored-by: Arc <ben@arc.wales>
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds support for a new category of browser-based extensions ('WASM extensions') in LNbits. It introduces a second manifest list, fetches extra configuration from URLs, and wires up permission checks before installing these extensions. There is no clear security bug in the diff, but the change expands the attack surface by adding a new extension type and by fetching remote config files. The code also contains a small duplication bug where the WASM manifest list is added twice in one place, which is likely harmless but shows the patch is fresh and partially incomplete.

Recommended action

Treat this as a feature commit that increases extension-system attack surface. Reviewers should verify that `fetch_release_config` enforces URL allowlists/SSRF protections, that `validate_extension_permissions` cannot be bypassed, and that the WASM runtime sandbox is properly isolated. The duplicated WASM manifest list should be cleaned up. No immediate security patch is required based solely on this diff.

Security signals we found

01

New remote manifest source added and merged into extension discovery

02

Arbitrary URL fetch introduced for extension release config (`fetch_release_config`)

03

Extension permissions now parsed from remote config and validated before release listing

04

WASM extensions require explicit permission grant and are excluded from batch update

05

Default WASM manifest URL points to a GitHub raw URL under the lnbits organization

06

Duplicated manifest list entry suggests patch is partial/fresh

Risk score

Why this scored 31/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 10/15
Confidence 4/10
Evidence quality 2/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.