CVE-2018-8073
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 · uneditedYii 2.x before 2.0.15 allows remote attackers to execute arbitrary LUA code via a variant of the CVE-2018-7269 attack in conjunction with the Redis extension.
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 confidenceYii 2.x before 2.0.15 contains a deserialization vulnerability in its Redis extension that allows remote attackers to execute arbitrary LUA code through a variant of CVE-2018-7269. The vulnerability stems from improper validation of Lua scripts passed to Redis, enabling attackers to inject and execute malicious Lua code on the server.
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< 2.0.15CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Yii 2.x installation and versionCheck the composer.json file in your project root for the 'yiisoft/yii2' package version, or look for the Version.php file in the Yii framework core directoryAffected if The installed Yii version is below 2.0.15 (e.g., 2.0.14, 2.0.13, etc.)
-
Confirm Redis extension is installedLook for the yiisoft/yii2-redis package in your composer.json file or check your vendor directory for yii2-redis componentsAffected if The yii2-redis extension is present in the project dependencies
-
Check Redis component configurationInspect your application configuration files (e.g., config/main.php, config/console.php) for the Redis component configuration under the 'components' or 'controllerMap' sectionAffected if A Redis component is configured and enabled in the application
-
Identify Lua script usage with RedisSearch your codebase for calls to Redis methods that execute Lua scripts, such as 'executeCommand("eval")', 'eval()', or custom Lua script invocations through the yii\redis\Connection classAffected if The application executes Lua scripts through the Redis connection, making it vulnerable to injection if the version is affected
-
Verify Redis network exposureCheck the Redis server bind address in your Redis configuration and whether the Yii application connects to a remote or local Redis instanceAffected if Redis is accessible over the network without proper access controls, increasing exploitability
You are affected if your application uses Yii 2.x with the Redis extension and your Yii version is below 2.0.15, particularly if Lua scripts are executed through the Redis connection.
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.
dbcve · scoped2.0.15
Upgrade Yii 2.x to version 2.0.15 or later. If immediate patching is not possible, restrict Redis access to trusted networks and implement input validation on Lua script parameters.
Yii 2.0.15
- Check your current Yii 2 version by examining your composer.json or running `composer show yiisoft/yii2`
- Update your composer.json to require "yiisoft/yii2": "2.0.15" or higher
- Run `composer update yiisoft/yii2` to apply the upgrade
- Verify the installed version is 2.0.15 or later with `composer show yiisoft/yii2`
- Test your application thoroughly, especially Redis-dependent functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8073 — 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-2018-8073 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