CVE-2010-4725 Code injection in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2010-4725 and fix it if it is affected.
What it is: CVE-2010-4725 is a critical code injection vulnerability in n/a, published on 3 Feb 2011. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-4725 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-2010-4725/ (Markdown: https://insights.sbomify.com/CVE-2010-4725/index.md)
Smarty template engine allows remote code execution if the non-default asp_tags option is enabled in php.ini.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- Available
What is CVE-2010-4725?
CVE-2010-4725 is a critical code injection vulnerability in n/a, published on 3 Feb 2011. It can be exploited over the network.
Official description
Smarty before 3.0.0 RC3 does not properly handle an on value of the asp_tags option in the php.ini file, which has unspecified impact and remote attack vectors.
Which versions are affected by CVE-2010-4725?
It affects 1 product.
Products include Smarty Smarty.
How do I fix CVE-2010-4725?
Upgrade to a fixed version.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2010-4725 being exploited?
There is no known exploitation of CVE-2010-4725 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2010-4725, GHSA-62jr-gjr6-pf9v.