# CVE-2023-3163: y_project RuoYi filterKeyword resource consumption

> Attackers can cause resource exhaustion in RuoYi via the filterKeyword function, leading to denial of service.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 8 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g3hh-q55f-9g3w

## What is CVE-2023-3163?

CVE-2023-3163 is a low-severity denial of service vulnerability in Ruoyi Ruoyi, published on 8 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in y_project RuoYi up to 4.7.7. It has been classified as problematic. Affected is the function filterKeyword. The manipulation of the argument value leads to resource consumption. VDB-231090 is the identifier assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including com.ruoyi:ruoyi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ruoyi:ruoyi` | Maven | All versions to 4.7.7 | None |
| `com.ruoyi:ruoyi` | Maven | All versions to 4.7.7 | None |

Products: Ruoyi Ruoyi.

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

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

## Is CVE-2023-3163 being exploited?

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

Public exploit code:

- A simple and quick way to check if your SQL Developer by Oracle is vulnerable to SQL Injection (CVE-2023-3163), most commonly occurs when SQL Developer version < 23.1.0. (github_poc): https://github.com/George0Papasotiriou/CVE-2023-3163-SQL-Injection-Prevention

## Other vulnerabilities in Ruoyi Ruoyi

- [CVE-2024-57521](https://insights.sbomify.com/CVE-2024-57521/): SQL injection in n/a (critical 10.0)
- [CVE-2025-28402](https://insights.sbomify.com/CVE-2025-28402/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28405](https://insights.sbomify.com/CVE-2025-28405/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28406](https://insights.sbomify.com/CVE-2025-28406/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-28408](https://insights.sbomify.com/CVE-2025-28408/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3163 is a low-severity denial of service vulnerability in Ruoyi Ruoyi, published on 8 Jun 2023. 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-2023-3163 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.ruoyi:ruoyi (Maven): affected all versions up to 4.7.7; no fix listed
- com.ruoyi:ruoyi (Maven): affected all versions up to 4.7.7; no fix listed

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

## Sources

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

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