# CVE-2024-2635: Multiple vulnerabilities on Meta4 HR from Cegid

> Attackers can access configuration pages to view file paths if the software is exposed to the internet, requiring removal of these pages or restricting access.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-m6qm-x65x-r3hh

## What is CVE-2024-2635?

CVE-2024-2635 is a high-severity vulnerability in Cegid Meta4 HR, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The configuration pages available are not intended to be placed on an Internet facing web server, as they expose file paths to the client, who can be an attacker. Instead of rewriting these pages to avoid this vulnerability, they will be dismissed from future releases of Cegid Meta4 HR, as they do not offer product functionality

Weakness: CWE-698 (Execution After Redirect (EAR))

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


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

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

## Is CVE-2024-2635 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2635 is a high-severity vulnerability in Cegid Meta4 HR, published on 19 Mar 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-2635 in the wild and no public exploit code.

Affected product: Cegid Meta4 HR. 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-2635/ (Markdown: https://insights.sbomify.com/CVE-2024-2635/index.md)
```

## Sources

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

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