CVE-2005-4198 SQL injection vulnerability in index.php in Netref 3.0 allows remote attackers to execute arbitrary SQL commands via the cat parameter.
High 7.5
Published
Updated
Check this codebase for CVE-2005-4198 and fix it if it is affected.
What it is: CVE-2005-4198 is a high-severity vulnerability in n/a, published on 13 Dec 2005.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4198 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-2005-4198/ (Markdown: https://insights.sbomify.com/CVE-2005-4198/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2005-4198?
CVE-2005-4198 is a high-severity vulnerability in n/a, published on 13 Dec 2005.
Official description
SQL injection vulnerability in index.php in Netref 3.0 allows remote attackers to execute arbitrary SQL commands via the cat parameter. NOTE: the provenance of this issue is unknown; the details were obtained solely from third party sources.
Weakness: CWE-89
Which versions are affected by CVE-2005-4198?
It affects 1 product.
Products include Netref Netref.
How do I fix CVE-2005-4198?
No fix has been published for CVE-2005-4198 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-4198 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4198 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
Sources
Also known as GHSA-7c3j-px25-gfc4.