CVE-2023-41631 File upload in n/a
High 8.8
Published
Updated
Check this codebase for CVE-2023-41631 and fix it if it is affected.
What it is: CVE-2023-41631 is a high-severity vulnerability in n/a, published on 17 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41631 exists.
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-2023-41631/ (Markdown: https://insights.sbomify.com/CVE-2023-41631/index.md)
Attackers can achieve remote code execution in eSST Monitoring by exploiting a vulnerability in the file upload function.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-41631?
CVE-2023-41631 is a high-severity vulnerability in n/a, published on 17 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
eSST Monitoring v2.147.1 was discovered to contain a remote code execution (RCE) vulnerability via the file upload function.
Weakness: CWE-434
Which versions are affected by CVE-2023-41631?
It affects 1 product.
Products include Esst Esst Monitoring.
How do I fix CVE-2023-41631?
No fix has been published for CVE-2023-41631 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-41631 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41631 exists.
Other vulnerabilities in n/a
Sources
Also known as GHSA-v986-xf39-cqrw.