dbcve.org
LemurApplication · Netflix

CVE-2015-7764

HIGH · 7.5 CVSS v3.1 Published 2017-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Lemur 0.1.4 does not use sufficient entropy in its IV when encrypting AES in CBC mode.

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 · high confidence

Lemur 0.1.4 uses AES in CBC mode but generates Initialization Vectors (IVs) with insufficient entropy. This predictability in IVs breaks the semantic security of CBC mode, potentially allowing attackers to detect repeated encryptions or mount chosen-plaintext attacks.

MitigationRegenerate the encryption implementation to use a cryptographically secure random number generator (CSPRNG) for IV generation, ensuring each encryption operation uses a unique, unpredictable IV. Re-encrypt any previously protected data with the corrected implementation.

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
LemurApplication
Affected:= 0.1.4

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lemur installation
    Locate the Lemur application on your system. This may be a Python package (check via 'pip list' or 'pip show lemur'), a Docker container, or a service running on your network.
    Affected if Lemur software is found on the system
  2. Determine installed version
    Run 'pip show lemur' or check your package manager to retrieve the installed version number of Netflix Lemur.
    Affected if The version displayed is 0.1.4 exactly
  3. Verify version matches CVE scope
    Compare your retrieved version against the affected range: Netflix Lemur version 0.1.4.
    Affected if Your installed version is exactly 0.1.4

You are affected if Netflix Lemur version 0.1.4 is installed in your environment, as this version uses predictable initialization vectors in AES-CBC encryption.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Regenerate the encryption implementation to use a cryptographically secure random number generator (CSPRNG) for IV generation, ensuring each encryption operation uses a unique, unpredictable IV. Re-encrypt any previously protected data with the corrected implementation.

Fix this in Lemur Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7764 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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