CVE-2015-1049 Other in n/a
Medium 6.8
Published
Updated
Check this codebase for CVE-2015-1049 and fix it if it is affected.
What it is: CVE-2015-1049 is a medium-severity vulnerability in n/a, published on 2 Feb 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2015-1049 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-2015-1049/ (Markdown: https://insights.sbomify.com/CVE-2015-1049/index.md)
Remote attackers can hijack sessions on Siemens SCALANCE X-200IRT switches, potentially taking over administrative accounts.
- 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-2015-1049?
CVE-2015-1049 is a medium-severity vulnerability in n/a, published on 2 Feb 2015. It can be exploited over the network.
Official description
The web server on Siemens SCALANCE X-200IRT switches with firmware before 5.2.0 allows remote attackers to hijack sessions via unspecified vectors.
Weakness: CWE-20
Which versions are affected by CVE-2015-1049?
It affects 1 product.
Products include Siemens Scalance X-200 Series Firmware.
How do I fix CVE-2015-1049?
No fix has been published for CVE-2015-1049 yet. Limit exposure of the affected software until one is available.
Is CVE-2015-1049 being exploited?
There is no known exploitation of CVE-2015-1049 in the wild and no public exploit code.
Sources
Also known as GHSA-jq2m-4x38-vgvr.