# CVE-2024-5354: anji-plus AJ-Report detailByCode information disclosure

> Remote attackers can exploit a flaw in AJ-Report's share token handling to disclose sensitive information without authentication.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 26 May 2024
- **Updated:** 1 Aug 2024

## What is CVE-2024-5354?

CVE-2024-5354 is a medium-severity vulnerability in anji-plus AJ-Report, published on 26 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in anji-plus AJ-Report up to 1.4.1. This vulnerability affects unknown code of the file /reportShare/detailByCode. The manipulation of the argument shareToken leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-266266 is the identifier assigned to this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-5354?

It affects 1 product.


Products: Anji-Plus Aj-Report.

## How do I fix CVE-2024-5354?

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

## Is CVE-2024-5354 being exploited?

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

## Other vulnerabilities in anji-plus AJ-Report

- [CVE-2022-46973](https://insights.sbomify.com/CVE-2022-46973/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-42983](https://insights.sbomify.com/CVE-2022-42983/): Auth bypass in n/a (high 8.8)
- [CVE-2024-5351](https://insights.sbomify.com/CVE-2024-5351/): anji-plus AJ-Report Javascript getValueFromJs deserialization (medium 5.3)
- [CVE-2024-5352](https://insights.sbomify.com/CVE-2024-5352/): anji-plus AJ-Report validationRules deserialization (medium 5.3)
- [CVE-2024-5353](https://insights.sbomify.com/CVE-2024-5353/): anji-plus AJ-Report ZIP File decompress path traversal (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5354 and fix it if it is affected.

What it is: CVE-2024-5354 is a medium-severity vulnerability in anji-plus AJ-Report, published on 26 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5354 in the wild and no public exploit code.

Affected product: anji-plus AJ-Report. 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-2024-5354/ (Markdown: https://insights.sbomify.com/CVE-2024-5354/index.md)
```

## Sources

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

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