# CVE-2020-14027: Other in n/a

> Attackers can exploit unsafe database connection arguments to enable rogue MySQL server attacks, potentially leading to data theft or code execution.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-53ph-mcf9-r8mc

## What is CVE-2020-14027?

CVE-2020-14027 is a medium-severity vulnerability in n/a, published on 22 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Ozeki NG SMS Gateway through 4.17.6. The database connection strings accept custom unsafe arguments, such as ENABLE_LOCAL_INFILE, that can be leveraged by attackers to enable MySQL Load Data Local (rogue MySQL server) attacks.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Ozeki Ozeki Ng Sms Gateway.

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

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

## Is CVE-2020-14027 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14022](https://insights.sbomify.com/CVE-2020-14022/): File upload in n/a (high 8.8)
- [CVE-2020-14025](https://insights.sbomify.com/CVE-2020-14025/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-14026](https://insights.sbomify.com/CVE-2020-14026/): Other in n/a (high 8.8)
- [CVE-2020-14029](https://insights.sbomify.com/CVE-2020-14029/): XML external entity in n/a (high 7.5)
- [CVE-2020-14030](https://insights.sbomify.com/CVE-2020-14030/): Deserialization in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14027 is a medium-severity vulnerability in n/a, published on 22 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14027 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-2020-14027/ (Markdown: https://insights.sbomify.com/CVE-2020-14027/index.md)
```

## Sources

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

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