Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2016-6519 medium CVSS 5.4

Cross-Site Scripting (XSS) in manila-ui (CVE-2016-6519)

Summary

Cross-site scripting in manila-ui (CVE-2016-6519). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.5.1 or later.

Original description

The description as published by the source.

Cross-site scripting (XSS) vulnerability in the "Shares" overview in Openstack Manila before 2.5.1 allows remote authenticated users to inject arbitrary web script or HTML via the Metadata field in the "Create Share" form.

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-2016-6519 has been found in manila-ui.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade manila-ui to 2.5.1 or later.
If unsure, ask your IT team or search "manila-ui CVE-2016-6519" on the vendor's site.

CVE-2016-6519 (manila-ui) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 2.5.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

Cross-site scripting (XSS) (CWE-79) exists in manila-ui.

📍 Affected scope

Check the vendor advisory for the affected versions of manila-ui.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.5.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 'manila-ui' . 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 'manila-ui' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade manila-ui to 2.5.1

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

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

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

Affected packages

PyPI manila-ui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5.1"}]}]

References

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