# CVE-2016-15021: nickzren alsdb sql injection

> An attacker can perform SQL injection in nickzren alsdb to read or modify data, requiring an upgrade to v2.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-r74c-ppq4-773h

## What is CVE-2016-15021?

CVE-2016-15021 is a medium-severity SQL injection vulnerability in nickzren alsdb, published on 17 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in nickzren alsdb. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to sql injection. Upgrading to version v2 is able to address this issue. The identifier of the patch is cbc79a68145e845f951113d184b4de207c341599. It is recommended to upgrade the affected component. The identifier VDB-218429 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2016-15021?

It affects 1 product.


Products: Columbia Als Data Browser.

## How do I fix CVE-2016-15021?

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

## Is CVE-2016-15021 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15021 and fix it if it is affected.

What it is: CVE-2016-15021 is a medium-severity SQL injection vulnerability in nickzren alsdb, published on 17 Jan 2023. 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-2016-15021 in the wild and no public exploit code.

Affected product: nickzren alsdb. 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-2016-15021/ (Markdown: https://insights.sbomify.com/CVE-2016-15021/index.md)
```

## Sources

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

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