Vulnerability in IBM Cloud Orchestrator services/[action]/launch API (CVE-2015-7494)
Summary
Vulnerability in IBM Cloud Orchestrator services/[action]/launch API (CVE-2015-7494). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability has been identified in IBM Cloud Orchestrator services/[action]/launch API. An authenticated domain admin user might modify cross domain resources via a /services/[action]/launch API call, provided it would have been possible for the domain admin user to gain access to a resource identifier of the other domain.
Source: NIST National Vulnerability Database NVD
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-2015-7494 has been found in IBM Cloud Orchestrator services/[action]/launch API.
Risk of unauthorized operations or information disclosure. CVSS score: 2.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "IBM Cloud Orchestrator services/[action]/launch API CVE-2015-7494" on the vendor's site.
CVE-2015-7494 (IBM Cloud Orchestrator services/[action]/launch API) — CWE-284 / CVSS v3 2.8
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.
A vulnerability (CWE-284) exists in IBM Cloud Orchestrator services/[action]/launch API.
Check the vendor advisory for the affected versions of IBM Cloud Orchestrator services/[action]/launch API.
Severity: Low (CVSS 2.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで IBM Cloud Orchestrator services/[action]/launch API を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- patch ibm.com