# CVE-2014-9563: Other in n/a

> Authenticated attackers can inject CRLF sequences to modify the root password and access the debug port on Unify IP phones.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cf58-jjq5-73mm

## What is CVE-2014-9563?

CVE-2014-9563 is a medium-severity vulnerability in n/a, published on 12 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CRLF injection vulnerability in the web-based management (WBM) interface in Unify (former Siemens) OpenStage SIP and OpenScape Desk Phone IP V3 devices before R3.32.0 allows remote authenticated users to modify the root password and consequently access the debug port using the serial interface via the ssh-password parameter to page.cmd.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2014-9563?

It affects 2 products.


Products: Unify Openscape Desk Phone Ip Sip, Unify Openstage Sip.

## How do I fix CVE-2014-9563?

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

## Is CVE-2014-9563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8422](https://insights.sbomify.com/CVE-2014-8422/): Weak cryptography in n/a (high 8.1)
- [CVE-2014-8421](https://insights.sbomify.com/CVE-2014-8421/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9563 and fix it if it is affected.

What it is: CVE-2014-9563 is a medium-severity vulnerability in n/a, published on 12 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9563 in the wild and no public exploit code.

Affected product: n/a. 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-2014-9563/ (Markdown: https://insights.sbomify.com/CVE-2014-9563/index.md)
```

## Sources

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

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