# CVE-2019-4299: Information disclosure in Robotic Process Automation with Automation Anywhere

> Local users can access sensitive data from log files if debugging is enabled in IBM Robotic Process Automation.

- **Severity:** Medium 5.1 (`CVSS:3.0/UI:N/I:N/AC:H/AV:L/PR:N/C:H/S:U/A:N/RL:O/E:U/RC:C`)
- **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:** 1 Jul 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qgvx-32f8-pq66

## What is CVE-2019-4299?

CVE-2019-4299 is a medium-severity vulnerability in IBM Robotic Process Automation with Automation Anywhere, published on 1 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Robotic Process Automation with Automation Anywhere 11 could allow a local user to obtain highly sensitive information from log files when debugging is enabled. IBM X-Force ID: 160765.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Ibm Robotic Process Automation With Automation Anywhere.

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

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

## Is CVE-2019-4299 being exploited?

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

## Other vulnerabilities in IBM Robotic Process Automation with Automation Anywhere

- [CVE-2018-1547](https://insights.sbomify.com/CVE-2018-1547/): Code injection in Robotic Process Automation with Automation Anywhere (high 8.0)
- [CVE-2019-4298](https://insights.sbomify.com/CVE-2019-4298/): Privilege escalation in Robotic Process Automation with Automation Anywhere (high 7.7)
- [CVE-2019-4336](https://insights.sbomify.com/CVE-2019-4336/): Security feature bypass in Robotic Process Automation with Automation Anywhere (high 7.5)
- [CVE-2019-4297](https://insights.sbomify.com/CVE-2019-4297/): Other in Robotic Process Automation with Automation Anywhere (medium 6.4)
- [CVE-2018-1876](https://insights.sbomify.com/CVE-2018-1876/): Information disclosure in Robotic Process Automation with Automation Anywhere (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4299 is a medium-severity vulnerability in IBM Robotic Process Automation with Automation Anywhere, published on 1 Jul 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-4299 in the wild and no public exploit code.

Affected product: IBM Robotic Process Automation with Automation Anywhere. 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-4299/ (Markdown: https://insights.sbomify.com/CVE-2019-4299/index.md)
```

## Sources

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

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