Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
stickerdaniel/linkedin-mcp-server
main @ aa19ba0
8
Fixes
0
CVEs
HIGH
Peak severity
66.7%
Coverage
Highlights
Denial of Service: 2 prior fixes. Scrutinize any change in this area.
linkedin_mcp_server/common_utils.py: most-fixed (2 issues). Treat as high-risk during review.
1 high-severity fix in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Insecure File Permissions: Playwright session states, browser profiles, and exported cookie files containing raw credentials were saved with insecure permissions, allowing other local users on the host system to extract active sessions.
Cleartext Storage of Sensitive Information: User credentials were historically stored as raw plaintext JSON files in the home directory before migrating to native system keychains. Any regression to disk-based configuration storage bypasses secure credential-store wrappers.
Denial of Service: Subprocess lookups to OS-level keyrings (like secret-tool for gnome-keyring) lacked execution timeouts. Under heavy loads or in headless environments where D-Bus blocks, the server threads hang indefinitely.