CVE-2002-1253 Abuse 2.00 and earlier allows local users to gain privileges via command line arguments that specify alternate Lisp scripts that run at esca
High 7.2
Published
Updated
Check this codebase for CVE-2002-1253 and fix it if it is affected.
What it is: CVE-2002-1253 is a high-severity vulnerability in n/a, published on 1 Sep 2004.
Exploitation: There is no known exploitation of CVE-2002-1253 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-2002-1253/ (Markdown: https://insights.sbomify.com/CVE-2002-1253/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2002-1253?
CVE-2002-1253 is a high-severity vulnerability in n/a, published on 1 Sep 2004.
Official description
Abuse 2.00 and earlier allows local users to gain privileges via command line arguments that specify alternate Lisp scripts that run at escalated privileges, which can contain functions that execute commands or modify files.
Which versions are affected by CVE-2002-1253?
It affects 1 product.
Products include Abuse Abuse.
How do I fix CVE-2002-1253?
No fix has been published for CVE-2002-1253 yet. Limit exposure of the affected software until one is available.
Is CVE-2002-1253 being exploited?
There is no known exploitation of CVE-2002-1253 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-254g-h6q6-4fxv.