# CVE-2020-35580: Path traversal in n/a

> Remote unauthenticated attackers can read arbitrary files and configuration data, including admin credentials, via a path traversal vulnerability in SearchBlox.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rxfx-hr79-qv8h

## What is CVE-2020-35580?

CVE-2020-35580 is a high-severity path traversal vulnerability in n/a, published on 20 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A local file inclusion vulnerability in the FileServlet in all SearchBlox before 9.2.2 allows remote, unauthenticated users to read arbitrary files from the operating system via a /searchblox/servlet/FileServlet?col=url= request. Additionally, this may be used to read the contents of the SearchBlox configuration file (e.g., searchblox/WEB-INF/config.xml), which contains both the Super Admin's API key and the base64 encoded SHA1 password hashes of other SearchBlox users.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Searchblox Searchblox.

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

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

## Is CVE-2020-35580 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-35580 exists.

Public exploit code:

- SearchBlox <9.2.2 - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-35580.yaml

## Other vulnerabilities in n/a

- [CVE-2015-7919](https://insights.sbomify.com/CVE-2015-7919/): SearchBlox 8.3 before 8.3.1 allows remote attackers to write to the config file, and consequently cause a denial of service (application cra (critical 10.0)
- [CVE-2020-10131](https://insights.sbomify.com/CVE-2020-10131/): CVE-2020-10131 (critical 9.8)
- [CVE-2018-11586](https://insights.sbomify.com/CVE-2018-11586/): XML external entity in n/a (critical 9.8)
- [CVE-2020-10129](https://insights.sbomify.com/CVE-2020-10129/): CVE-2020-10129 (high 8.8)
- [CVE-2020-10130](https://insights.sbomify.com/CVE-2020-10130/): CVE-2020-10130 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35580 is a high-severity path traversal vulnerability in n/a, published on 20 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-35580 exists.

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-2020-35580/ (Markdown: https://insights.sbomify.com/CVE-2020-35580/index.md)
```

## Sources

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

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