# CVE-2019-18958: Other in n/a

> Nitro Pro creates a debug log file that can be edited and executed, potentially allowing arbitrary code execution if the file is manipulated.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 21 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j395-6955-mv56

## What is CVE-2019-18958?

CVE-2019-18958 is a high-severity vulnerability in n/a, published on 21 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nitro Pro before 13.2 creates a debug.log file in the directory where a .pdf file is located, if the .pdf document was produced by an OCR operation on the JPEG output of a scanner. Reportedly, this can have a security risk if debug.log is later edited and then executed.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Gonitro Nitro Pro.

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

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

## Is CVE-2019-18958 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-21796](https://insights.sbomify.com/CVE-2021-21796/): Use after free in Nitro Pro (high 8.8)
- [CVE-2021-21797](https://insights.sbomify.com/CVE-2021-21797/): Use after free in Nitro Pro (high 8.8)
- [CVE-2021-21798](https://insights.sbomify.com/CVE-2021-21798/): Use after free in Nitro Pro (high 8.8)
- [CVE-2020-6112](https://insights.sbomify.com/CVE-2020-6112/): Memory corruption in Nitro Pro (high 8.8)
- [CVE-2020-6113](https://insights.sbomify.com/CVE-2020-6113/): Integer overflow in Nitro Pro (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18958 is a high-severity vulnerability in n/a, published on 21 Nov 2019. 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-2019-18958 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-18958/ (Markdown: https://insights.sbomify.com/CVE-2019-18958/index.md)
```

## Sources

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

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