Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2017-5936 high CVSS 7.5

Vulnerability in nova-lxd (CVE-2017-5936)

Summary

Vulnerability in nova-lxd (CVE-2017-5936). Data can be tampered with by attackers. Mitigation: upgrade to 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1 or later.

Original description

The description as published by the source.

OpenStack Nova-LXD before 13.1.1 uses the wrong name for the veth pairs when applying Neutron security group rules for instances, which allows remote attackers to bypass intended security restrictions.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2017-5936 has been found in nova-lxd.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade nova-lxd to 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1 or later.
If unsure, ask your IT team or search "nova-lxd CVE-2017-5936" on the vendor's site.

CVE-2017-5936 (nova-lxd) — CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in nova-lxd.

📍 Affected scope

Check the vendor advisory for the affected versions of nova-lxd.

🔥 Severity

Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nova-lxd' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'nova-lxd' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nova-lxd を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade nova-lxd to 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1

    ステージング環境で 1b76cefb92081efa1e88cd8f330253f857028bd2, 13.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI nova-lxd
[{"repo":"https:\/\/github.com\/openstack\/nova-lxd","type":"GIT","events":[{"introduced":"0"},{"fixed":"1b76cefb92081efa1e88cd8f330253f857028bd2"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details