CVE-2024-46505 Business logic in n/a
Critical 9.1
Published
Updated
Check this codebase for CVE-2024-46505 and fix it if it is affected.
What it is: CVE-2024-46505 is a critical vulnerability in n/a, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46505 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-2024-46505/ (Markdown: https://insights.sbomify.com/CVE-2024-46505/index.md)
A business logic flaw in Infoblox BloxOne thick client allows attackers to bypass security controls and potentially access sensitive data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-46505?
CVE-2024-46505 is a critical vulnerability in n/a, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Infoblox BloxOne v2.4 was discovered to contain a business logic flaw due to thick client vulnerabilities.
Which versions are affected by CVE-2024-46505?
How do I fix CVE-2024-46505?
No fix has been published for CVE-2024-46505 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-46505 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46505 exists.
Sources
Also known as GHSA-p4cr-4mjx-v45f.