# CVE-2017-10049: Cross-site scripting in Siebel Core - Server Framework

> Unauthenticated attackers can exploit a cross-site scripting flaw in Siebel CRM Search to read and modify accessible data via HTTP.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-j6qx-28h2-c6rr

## What is CVE-2017-10049?

CVE-2017-10049 is a medium-severity cross-site scripting vulnerability in Oracle Corporation Siebel Core - Server Framework, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Siebel Core CRM component of Oracle Siebel CRM (subcomponent: Search). Supported versions that are affected are 16.0 and 17.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Siebel Core CRM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Siebel Core CRM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Siebel Core CRM accessible data as well as unauthorized read access to a subset of Siebel Core CRM accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2017-10049?

It affects 1 product.


Products: Oracle Siebel Core-Server Framework.

## How do I fix CVE-2017-10049?

No fix has been published for CVE-2017-10049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10049 being exploited?

There is no known exploitation of CVE-2017-10049 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation Siebel Core - Server Framework

- [CVE-2016-5461](https://insights.sbomify.com/CVE-2016-5461/): Information disclosure in n/a (medium 6.5)
- [CVE-2017-10162](https://insights.sbomify.com/CVE-2017-10162/): Missing authorization in Siebel Core - Server Framework (medium 5.4)
- [CVE-2016-5456](https://insights.sbomify.com/CVE-2016-5456/): Information disclosure in n/a (medium 5.3)
- [CVE-2018-2789](https://insights.sbomify.com/CVE-2018-2789/): Information disclosure in Siebel Core - Server Framework (medium 5.0)
- [CVE-2016-3450](https://insights.sbomify.com/CVE-2016-3450/): Information disclosure in n/a (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10049 and fix it if it is affected.

What it is: CVE-2017-10049 is a medium-severity cross-site scripting vulnerability in Oracle Corporation Siebel Core - Server Framework, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-10049 in the wild and no public exploit code.

Affected product: Oracle Corporation Siebel Core - Server Framework. 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-2017-10049/ (Markdown: https://insights.sbomify.com/CVE-2017-10049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10049
- OSV: https://osv.dev/vulnerability/CVE-2017-10049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-10049/
Summaries are generated and may contain mistakes; the official description above is the record.