# CVE-2019-13028: Code injection in n/a

> Remote attackers can execute arbitrary code or delete files via a crafted HTML page due to incorrect local web server implementation in the Slovak eID client.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8j2g-chhr-59j5

## What is CVE-2019-13028?

CVE-2019-13028 is a high-severity code injection vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An incorrect implementation of a local web server in eID client (Windows version before 3.1.2, Linux version before 3.0.3) allows remote attackers to execute arbitrary code (.cgi, .pl, or .php) or delete arbitrary files via a crafted HTML page. This is a product from the Ministry of Interior of the Slovak Republic.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2019-13028?

It affects 1 product.


Products: Minv Electronic Identification Cards Client.

## How do I fix CVE-2019-13028?

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

## Is CVE-2019-13028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13028 and fix it if it is affected.

What it is: CVE-2019-13028 is a high-severity code injection vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-13028 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-2019-13028/ (Markdown: https://insights.sbomify.com/CVE-2019-13028/index.md)
```

## Sources

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

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