# CVE-2010-1591: Privilege escalation in n/a

> Local attackers can gain elevated privileges by sending crafted IOCTL requests to vulnerable Rising Antivirus kernel drivers.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 28 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6m4q-47fc-c7jm

## What is CVE-2010-1591?

CVE-2010-1591 is a high-severity vulnerability in n/a, published on 28 Apr 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Beijing Rising International Rising Antivirus 2008 through 2010 does not properly validate input to certain IOCTLs, including 0x83003C07, which allows local users to gain privileges via crafted IOCTL requests to the (1) HookCont.sys, (2) HookNtos.sys, (3) HOOKREG.sys, or (4) HookSys.sys device driver; or the (5) RsNTGdi.sys kernel module, reachable through \Device\RSNTGDI.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-1591?

It affects 1 product.


Products: Rising-Global Rising Antivirus.

## How do I fix CVE-2010-1591?

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

## Is CVE-2010-1591 being exploited?

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

Public exploit code:

- Rising AntiVirus 2008/2009/2010 - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5539](https://insights.sbomify.com/CVE-2008-5539/): Security feature bypass in n/a (critical 9.3)
- [CVE-2008-1738](https://insights.sbomify.com/CVE-2008-1738/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1591 and fix it if it is affected.

What it is: CVE-2010-1591 is a high-severity vulnerability in n/a, published on 28 Apr 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1591 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-2010-1591/ (Markdown: https://insights.sbomify.com/CVE-2010-1591/index.md)
```

## Sources

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

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