CVE-2003-0363 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2003-0363 and fix it if it is affected.
What it is: CVE-2003-0363 is a high-severity vulnerability in n/a, published on 15 Apr 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0363 in the wild and no public exploit code.
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-2003-0363/ (Markdown: https://insights.sbomify.com/CVE-2003-0363/index.md)
Remote attackers can exploit a format string vulnerability in LICQ to potentially execute arbitrary code or cause other unknown impacts.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2003-0363?
CVE-2003-0363 is a high-severity vulnerability in n/a, published on 15 Apr 2005. It can be exploited over the network, with no action from the victim.
Official description
Format string vulnerability in LICQ 1.2.6, 1.0.3 and possibly other versions allows remote attackers to perform unknown actions via format string specifiers.
Which versions are affected by CVE-2003-0363?
It affects 1 product.
Products include Licq Licq.
How do I fix CVE-2003-0363?
No fix has been published for CVE-2003-0363 yet. Limit exposure of the affected software until one is available.
Is CVE-2003-0363 being exploited?
There is no known exploitation of CVE-2003-0363 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-9hfx-gwch-cr6c.