# CVE-2017-3631: Memory corruption in Solaris Operating System

> A local low-privileged attacker can exploit a kernel memory corruption flaw in Solaris to read, modify data, or cause partial denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2017
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-hm92-g5hw-f54f

## What is CVE-2017-3631?

CVE-2017-3631 is a medium-severity memory corruption vulnerability in Oracle Solaris, published on 22 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel). The supported version that is affected is 11. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Solaris executes to compromise Solaris. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Solaris accessible data as well as unauthorized read access to a subset of Solaris accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Solaris. CVSS 3.0 Base Score 5.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Oracle Solaris.

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

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

## Is CVE-2017-3631 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3631 exists.

Public exploit code:

- Solaris RSH Stack Clash Privilege Escalation (metasploit)
- Oracle Solaris 11.1/11.3 (RSH) - 'Stack Clash' Local Privilege Escalation (exploitdb)
- Solaris - RSH Stack Clash Privilege Escalation (Metasploit) (exploitdb)
- Solaris - RSH Stack Clash Privilege Escalation (Metasploit) (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-2017-3623](https://insights.sbomify.com/CVE-2017-3623/): Other in Solaris Operating System (critical 10.0)
- [CVE-2014-0397](https://insights.sbomify.com/CVE-2014-0397/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3631 is a medium-severity memory corruption vulnerability in Oracle Solaris, published on 22 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3631 exists.

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-3631/ (Markdown: https://insights.sbomify.com/CVE-2017-3631/index.md)
```

## Sources

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

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