CVE-2009-2038 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2009-2038 and fix it if it is affected.
What it is: CVE-2009-2038 is a critical vulnerability in n/a, published on 12 Jun 2009.
Exploitation: There is no known exploitation of CVE-2009-2038 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-2009-2038/ (Markdown: https://insights.sbomify.com/CVE-2009-2038/index.md)
Unspecified vulnerability in the Finnish Bank Payment module for osCommerce with unknown impact and attack vectors.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2009-2038?
CVE-2009-2038 is a critical vulnerability in n/a, published on 12 Jun 2009.
Official description
Unspecified vulnerability in the Finnish Bank Payment module 2.2 for osCommerce has unknown impact and attack vectors related to bank charges.
Which versions are affected by CVE-2009-2038?
It affects 1 product.
Products include Oscommerce Finnish Bank Payment.
How do I fix CVE-2009-2038?
No fix has been published for CVE-2009-2038 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-2038 being exploited?
There is no known exploitation of CVE-2009-2038 in the wild and no public exploit code.
Sources
Also known as GHSA-v5fw-2fjr-vhg3.