# CVE-2020-4708: Misconfiguration in Security Trusteer Pinpoint Detect

> An attacker can read sensitive information due to a wildcard CORS configuration in IBM Security Trusteer Pinpoint Detect.

- **Severity:** Low 3.7 (`CVSS:3.0/AC:H/S:U/AV:N/A:N/I:N/PR:N/C:L/UI:N/RL:O/E:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-924w-c7p6-hr3m

## What is CVE-2020-4708?

CVE-2020-4708 is a low-severity vulnerability in IBM Security Trusteer Pinpoint Detect, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Security Trusteer Pinpoint Detect 11.6.5 could disclose some information due to using a wildcard in the Access-Control-Allow-Origin header. IBM X-Force ID: 187371.

## Which versions are affected by CVE-2020-4708?

It affects 1 product.


Products: Ibm Security Trusteer Pinpoint Detect.

## How do I fix CVE-2020-4708?

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

## Is CVE-2020-4708 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4708 and fix it if it is affected.

What it is: CVE-2020-4708 is a low-severity vulnerability in IBM Security Trusteer Pinpoint Detect, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-4708 in the wild and no public exploit code.

Affected product: IBM Security Trusteer Pinpoint Detect. 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-2020-4708/ (Markdown: https://insights.sbomify.com/CVE-2020-4708/index.md)
```

## Sources

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

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