# CVE-2018-15612: Orchestration Designer Runtime Config CSRF

> Attackers can modify administrative settings in Avaya Aura Orchestration Designer via CSRF, potentially escalating privileges or altering configurations.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qcf9-f8qc-c69h

## What is CVE-2018-15612?

CVE-2018-15612 is a high-severity vulnerability in Avaya Orchestration Designer, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A CSRF vulnerability in the Runtime Config component of Avaya Aura Orchestration Designer could allow an attacker to add, change, or remove administrative settings. Affected versions of Avaya Aura Orchestration Designer include all versions up to 7.2.1.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-15612?

It affects 1 product.


Products: Avaya Orchestration Designer.

## How do I fix CVE-2018-15612?

No fix has been published for CVE-2018-15612 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-15612 being exploited?

There is no known exploitation of CVE-2018-15612 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15612 and fix it if it is affected.

What it is: CVE-2018-15612 is a high-severity vulnerability in Avaya Orchestration Designer, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-15612 in the wild and no public exploit code.

Affected product: Avaya Orchestration Designer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-15612/ (Markdown: https://insights.sbomify.com/CVE-2018-15612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-15612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-15612
- OSV: https://osv.dev/vulnerability/CVE-2018-15612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-15612/
Summaries are generated and may contain mistakes; the official description above is the record.