Skip to content

Critical vulnerability found in cron-utils

Critical severity GitHub Reviewed Published Nov 15, 2021 in jmrozanec/cron-utils • Updated Feb 1, 2023

Package

maven com.cronutils:cron-utils (Maven)

Affected versions

< 9.1.6

Patched versions

9.1.6

Description

Impact

A Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.

Patches

The issue was patched and a new version was released. Please upgrade to version 9.1.6.

Workarounds

There are no known workarounds up to this moment.

References

A description of the issue is provided in issue 461

For more information

If you have any questions or comments about this advisory:

Open an issue in the cron-utils Github repository

References

@jmrozanec jmrozanec published to jmrozanec/cron-utils Nov 15, 2021
Published by the National Vulnerability Database Nov 15, 2021
Reviewed Nov 15, 2021
Published to the GitHub Advisory Database Nov 15, 2021
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

5.666%
(94th percentile)

Weaknesses

CVE ID

CVE-2021-41269

GHSA ID

GHSA-p9m8-27x8-rg87

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.