Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-26238

Vulnerability in com.cronutils:cron-utils (CVE-2020-26238)

Summary

Vulnerability in com.cronutils:cron-utils (CVE-2020-26238). Confidential information can be exposed externally. Mitigation: upgrade to 9.1.3 or later.

Original description

The description as published by the source.

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 released. Please upgrade to version 9.1.3.

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:

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-26238 has been found in com.cronutils:cron-utils.
Confidential information can be exposed externally.
What to do: upgrade com.cronutils:cron-utils to 9.1.3 or later.
If unsure, ask your IT team or search "com.cronutils:cron-utils CVE-2020-26238" on the vendor's site.

CVE-2020-26238 (com.cronutils:cron-utils) — CWE-74
Attack vector: local
Patched: 9.1.3 — apply immediately
Workaround: There are no known workarounds up to this moment.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-74) exists in com.cronutils:cron-utils.

📍 Affected scope

Check the vendor advisory for the affected versions of com.cronutils:cron-utils.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 9.1.3.

🛡️ Workaround

Workaround: There are no known workarounds up to this moment.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.cronutils:cron-utils を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    There are no known workarounds up to this moment.

    パッチが適用されるまでの応急処置として、There are no known workarounds up to this moment. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade com.cronutils:cron-utils to 9.1.3

    ステージング環境で 9.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.cronutils:cron-utils
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details