# CVE-2024-30614: Information disclosure in n/a

> Attackers can obtain sensitive information via exposed resources in the error scope of Ametys CMS.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-8fj4-3988-99m9

## What is CVE-2024-30614?

CVE-2024-30614 is a medium-severity vulnerability in n/a, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Ametys CMS v4.5.0 and before allows attackers to obtain sensitive information via exposed resources to the error scope.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Ametys Ametys.

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

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

## Is CVE-2024-30614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16935](https://insights.sbomify.com/CVE-2017-16935/): Missing authorization in n/a (critical 9.8)
- [CVE-2022-26159](https://insights.sbomify.com/CVE-2022-26159/): Information disclosure in n/a (medium 5.3)
- [CVE-2022-50937](https://insights.sbomify.com/CVE-2022-50937/): Ametys CMS v4.4.1 - Cross Site Scripting (XSS) (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30614 is a medium-severity vulnerability in n/a, published on 12 Apr 2024. 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-2024-30614 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-2024-30614/ (Markdown: https://insights.sbomify.com/CVE-2024-30614/index.md)
```

## Sources

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

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