OpenstackApplication · Redhat
CVE-2016-2121
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA permissions flaw was found in redis, which sets weak permissions on certain files and directories that could potentially contain sensitive information. A local, unprivileged user could possibly use this flaw to access unauthorized system information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRedis sets weak permissions on certain files and directories that could contain sensitive information such as configuration data, keys, or cached data. A local unprivileged user could read these improperly protected files to gain unauthorized access to system information or application data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenstackApplication
= 10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Redis installation and versionRun 'redis-server --version' or check the redis package via 'rpm -qa | grep -i redis'Affected if Redis is installed and version matches affected Redhat Openstack 10 release
-
Locate Redis configuration filesCheck common config locations: /etc/redis/, /etc/, or run 'find / -name redis.conf 2>/dev/null' to locate all config filesAffected if Redis configuration files exist on the system
-
Check permissions on Redis configuration filesRun 'ls -la /etc/redis/redis.conf' or similar path, and 'stat -c "%a %n" /path/to/redis.conf'Affected if Permissions are 644 or weaker (world-readable or group-readable)
-
Check permissions on Redis data directoriesRun 'ls -la' on /var/lib/redis or the configured data directory; check for world-readable or group-readable permissionsAffected if Data directory permissions are 755 or weaker
-
Check permissions on Redis key filesLocate .rdb dump files or RDB/AOF files in data directory, then run 'ls -la' to inspect their octal permissionsAffected if Key or dump files have permissions 644 or weaker, allowing unprivileged users to read sensitive data
User is affected if Redis is installed with configuration or data files that have weak permissions (world-readable or group-readable), allowing unprivileged local users to access sensitive data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataConfigure Redis and the operating system to enforce strict file permissions (e.g., 600 for sensitive files, 700 for directories) on Redis data and configuration files, ensuring only the redis user has access.
Fix this in Openstack
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2121 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data