CVE-2013-7458: linenoise, as used in Redis before 3.2.3, uses world-readable permissions for .rediscli_history, which allo...

Security readout for executives and security teams

Redis CLI history files could be created so other local users could read them. If administrators typed passwords, connection strings, or sensitive commands into redis-cli, those values may have been exposed on shared systems. This is a local information-disclosure issue, not evidence of remote compromise. Exposure is most likely on hosts running Redis before 3.2.3 or older vendor-packaged Redis builds where redis-cli was used interactively. Risk rises on shared Linux systems, jump hosts, development servers, or operations boxes with multiple local users. Treat as a focused hygiene and credential-exposure issue. Prioritize shared administration hosts and environments where Redis passwords may have been typed interactively. It does not warrant emergency RCE-style response based on the supplied evidence. Mitigation focus: Upgrade Redis to 3.2.3 or a vendor-patched package.; Follow Debian, openSUSE, or your platform vendor advisory guidance.; Restrict permissions on existing .rediscli_history files..

Prepared

Jun 13, 2026, 14:00 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.