First published: Tue Nov 24 2020(Updated: )
A flaw was found in cron-utils. End applications passing unsanitized user input which is subsequently parsed by the `@Cron` annotation can allow an attacker to execute arbitrary expressions using JavaEL which will be implicitly executed by the constraint validator. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cron-utils Project Cron-utils | <9.1.3 | |
IBM Data Virtualization on Cloud Pak for Data | <=3.0 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.2 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.1 | |
IBM Watson Query with Cloud Pak for Data as a Service | <=2.0 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.8 | |
IBM Data Virtualization on Cloud Pak for Data | <=1.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-26238 is considered a high severity vulnerability due to the potential for arbitrary code execution through unsanitized user input.
To fix CVE-2020-26238, ensure you are using an updated version of cron-utils that is above 9.1.3 that sanitizes user input properly.
CVE-2020-26238 affects cron-utils versions up to 9.1.3 and IBM products including Data Virtualization and Watson Query on specific versions.
CVE-2020-26238 can facilitate arbitrary code execution attacks using JavaEL through unvalidated user input.
As of now, there are no widely reported exploits for CVE-2020-26238, but the vulnerability's nature poses a significant risk.