CVE-2019-4299

CVE-2019-4299 is a medium-severity vulnerability in Ibm Robotic Process Automation With Automation Anywhere with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

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.

Frequently asked questions

What is CVE-2019-4299?
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.
How severe is CVE-2019-4299?
CVE-2019-4299 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-4299 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-4299?
CVE-2019-4299 affects Ibm Robotic Process Automation With Automation Anywhere. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-4299?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-4299 published?
CVE-2019-4299 was published on 2019-07-01 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Robotic Process Automation With Automation Anywhere

All CVEs affecting Ibm Robotic Process Automation With Automation Anywhere →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →