CVE-2010-1007 Information disclosure in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2010-1007 and fix it if it is affected.
What it is: CVE-2010-1007 is a medium-severity vulnerability in n/a, published on 19 Mar 2010. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-1007 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-1007/ (Markdown: https://insights.sbomify.com/CVE-2010-1007/index.md)
Remote attackers can obtain sensitive information from the Power Extension Manager extension for TYPO3.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2010-1007?
CVE-2010-1007 is a medium-severity vulnerability in n/a, published on 19 Mar 2010. It can be exploited over the network.
Official description
Unspecified vulnerability in the Power Extension Manager (ch_lightem) extension 1.0.34 and earlier for TYPO3 allows remote attackers to obtain sensitive information via unknown vectors.
Weakness: CWE-200
Which versions are affected by CVE-2010-1007?
It affects 1 product.
Products include Chi Hoang Ch Lightem.
How do I fix CVE-2010-1007?
No fix has been published for CVE-2010-1007 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-1007 being exploited?
There is no known exploitation of CVE-2010-1007 in the wild and no public exploit code.
Sources
Also known as GHSA-fr2q-2fcw-85pj.