Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2017-7549 medium CVSS 6.4

Vulnerability in instack-undercloud (CVE-2017-7549)

Summary

Vulnerability in instack-undercloud (CVE-2017-7549). Confidential information can be exposed externally.

Original description

The description as published by the source.

A flaw was found in instack-undercloud 7.2.0 as packaged in Red Hat OpenStack Platform Pike, 6.1.0 as packaged in Red Hat OpenStack Platform Oacta, 5.3.0 as packaged in Red Hat OpenStack Newton, where pre-install and security policy scripts used insecure temporary files. A local user could exploit this flaw to conduct a symbolic-link attack, allowing them to overwrite the contents of arbitrary files.

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-7549 has been found in instack-undercloud.
Confidential information can be exposed externally. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "instack-undercloud CVE-2017-7549" on the vendor's site.

CVE-2017-7549 (instack-undercloud) — CWE-377 / CVSS v3 6.4
Attack vector: local / no user interaction
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 (CWE-377) exists in instack-undercloud.

📍 Affected scope

Check the vendor advisory for the affected versions of instack-undercloud.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 'instack-undercloud' . 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 'instack-undercloud' . | grep -v node_modules

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

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

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

Affected packages

PyPI instack-undercloud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"7.2.0"}]}]
PyPI instack
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"7.2.0"},{"last_affected":"6.1.0"},{"last_affected":"5.3.0"}]}]
pip instack-undercloud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

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