# CVE-2023-25355: Privilege escalation in n/a

> A local attacker with daemon user access can overwrite service files to escalate privileges to root on sipXcom servers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-wp73-jjrg-gp39

## What is CVE-2023-25355?

CVE-2023-25355 is a high-severity vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CoreDial sipXcom up to and including 21.04 is vulnerable to Insecure Permissions. A user who has the ability to run commands as the `daemon` user on a sipXcom server can overwrite a service file, and escalate their privileges to `root`.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-25355?

It affects 1 product.


Products: Coredial Sipxcom.

## How do I fix CVE-2023-25355?

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

## Is CVE-2023-25355 being exploited?

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

Public exploit code:

- CVE-2023-25355 and CVE-2023-25356 with automated service reload (github_poc): https://github.com/glefait/CVE-2023-25355-25356

## Other vulnerabilities in n/a

- [CVE-2023-25356](https://insights.sbomify.com/CVE-2023-25356/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25355 and fix it if it is affected.

What it is: CVE-2023-25355 is a high-severity vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25355 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-2023-25355/ (Markdown: https://insights.sbomify.com/CVE-2023-25355/index.md)
```

## Sources

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

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