Skip to content

fix: a hardcoded plex api token is embedded in plain... in Pluto.m3u - #34

Open
anupamme wants to merge 1 commit into
iprtl:livefrom
anupamme:fix-repo-m3u-v-001-redact-plex-token
Open

fix: a hardcoded plex api token is embedded in plain... in Pluto.m3u#34
anupamme wants to merge 1 commit into
iprtl:livefrom
anupamme:fix-repo-m3u-v-001-redact-plex-token

Conversation

@anupamme

Copy link
Copy Markdown

Summary

Fix high severity security issue in Pluto.m3u.

Vulnerability

Field Value
ID V-001
Severity HIGH
Scanner multi_agent_ai
Rule V-001
File Pluto.m3u:124
Assessment Likely exploitable
Chain Complexity 2-step

Description: A hardcoded Plex API token is embedded in plaintext within the Pluto.m3u playlist configuration file. The token 'xePfG98DiSxDoEPoY91x' appears in URL parameters for Plex.tv EPG (Electronic Program Guide) service access, exposed to anyone with repository or file read access.

Evidence

Exploitation scenario: An attacker with read access extracts the token from the URL parameter in Pluto.m3u.

Scanner confirmation: multi_agent_ai rule V-001 flagged this pattern.

Production code: This file is in the production codebase, not test-only code.

Changes

  • Pluto.m3u

Behavior Preservation

The change is scoped to 1 file on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.


Automated security fix by OrbisAI Security

Automated security fix generated by OrbisAI Security
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant