# CVE-2017-3623: Other in Solaris Operating System

> Unauthenticated remote attackers can compromise Solaris systems via the Kernel RPC component, leading to full system takeover.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-79mg-vr9v-4r75

## What is CVE-2017-3623?

CVE-2017-3623 is a critical vulnerability in Oracle Solaris, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel RPC). For supported versions that are affected see note. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Solaris. While the vulnerability is in Solaris, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Solaris. Note: CVE-2017-3623 is assigned for "Ebbisland". Solaris 10 systems which have had any Kernel patch installed after, or updated via patching tools since 2012-01-26 are not impacted. Also, any Solaris 10 system installed with Solaris 10 1/13 (Solaris 10 Update 11) are not vulnerable. Solaris 11 is not impacted by this issue. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

## Which versions are affected by CVE-2017-3623?

It affects 1 product.


Products: Oracle Solaris.

## How do I fix CVE-2017-3623?

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

## Is CVE-2017-3623 being exploited?

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

Public exploit code:

- EBBISLAND EBBSHAVE 6100-09-04-1441 - Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in Oracle Solaris

- [CVE-2020-14871](https://insights.sbomify.com/CVE-2020-14871/): Oracle Solaris and Zettabyte File System (ZFS) Unspecified (critical 10.0, exploited in the wild)
- [CVE-2019-3010](https://insights.sbomify.com/CVE-2019-3010/): Oracle Solaris Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2026-46978](https://insights.sbomify.com/CVE-2026-46978/): Missing authorization in Oracle Solaris (critical 10.0)
- [CVE-2014-0397](https://insights.sbomify.com/CVE-2014-0397/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-3509](https://insights.sbomify.com/CVE-2010-3509/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3623 and fix it if it is affected.

What it is: CVE-2017-3623 is a critical vulnerability in Oracle Solaris, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3623 in the wild and no public exploit code.

Affected product: Oracle Solaris. 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-2017-3623/ (Markdown: https://insights.sbomify.com/CVE-2017-3623/index.md)
```

## Sources

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

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