# CVE-2020-27660: SQL injection in Safe Access

> Remote attackers can execute arbitrary SQL commands via the domain parameter in Synology Safe Access, potentially compromising database integrity and confidentiality.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cp77-jfvp-qpxx

## What is CVE-2020-27660?

CVE-2020-27660 is a critical SQL injection vulnerability in Synology Safe Access, published on 30 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SQL injection vulnerability in request.cgi in Synology SafeAccess before 1.2.3-0234 allows remote attackers to execute arbitrary SQL commands via the domain parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Synology Safeaccess.

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

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

## Is CVE-2020-27660 being exploited?

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

## Other vulnerabilities in Synology Safe Access

- [CVE-2020-27659](https://insights.sbomify.com/CVE-2020-27659/): Cross-site scripting in Safe Access (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27660 is a critical SQL injection vulnerability in Synology Safe Access, published on 30 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27660 in the wild and no public exploit code.

Affected product: Synology Safe Access. 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-27660/ (Markdown: https://insights.sbomify.com/CVE-2020-27660/index.md)
```

## Sources

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

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