CVE-2023-41613 Other in n/a
High 7.8
Published
Updated
Check this codebase for CVE-2023-41613 and fix it if it is affected.
What it is: CVE-2023-41613 is a high-severity vulnerability in n/a, published on 4 Dec 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41613 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-41613/ (Markdown: https://insights.sbomify.com/CVE-2023-41613/index.md)
EzViz Studio is vulnerable to DLL hijacking, allowing attackers to execute arbitrary code via malicious library loading.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2023-41613?
CVE-2023-41613 is a high-severity vulnerability in n/a, published on 4 Dec 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
EzViz Studio v2.2.0 is vulnerable to DLL hijacking.
Weakness: CWE-427
Which versions are affected by CVE-2023-41613?
It affects 1 product.
Products include Ezviz Ezviz Studio.
How do I fix CVE-2023-41613?
No fix has been published for CVE-2023-41613 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-41613 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41613 exists.
Sources
Also known as GHSA-qm5v-ggqm-6gpg.