Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
multiversx/mx-chain-proxy-go
master @ f9c9ac2
7
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 3 prior fixes. Scrutinize any change in this area.
api: most-fixed (2 issues). Treat as high-risk during review.
5 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: The application historically exposed sensitive endpoints (such as observer reloads and staking information) without enforcing credentials, or used insecure basic authentication handlers. Failure to properly register and secure API route definitions allows unauthorized actors to trigger privileged actions.
Credential Leak: Shipping configuration templates with default credentials or active placeholder PEM key files within the repository increases the risk of immediate compromise if deployed without adjustment. Missing server-side checks to reject default configurations allows deployments to remain insecure.
Denial of Service: Making outbound HTTP calls to network observers without proper connection read deadlines or response caching mechanisms exposes the proxy to thread and connection pool exhaustion when external observers respond slowly or hang.