CVE-2024-42681: Improper Preservation of Permissions in xxl-job

com.xuxueli:xxl-job-core Updated 02 Oct 2025

Summary

15/08/2024
Yes i
High
8.8

CVE-2024-42681: Improper Preservation of Permissions in xxl-job. Affects com.xuxueli:xxl-job-core versions < 2.4.2. Fixed in 2.4.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

xxl-job is a Maven package that provides job scheduling and task execution capabilities. It is commonly used in Java applications to manage and execute background tasks. The package allows users to define and schedule tasks, which are then executed by the system. However, a vulnerability has been discovered in version 2.4.1 of xxl-job, which could allow a remote attacker to execute arbitrary code by exploiting the Sub-Task ID component.

Vulnerability Detail

The vulnerability in xxl-job version 2.4.1 is due to insecure permissions. It allows a remote attacker to execute arbitrary code by manipulating the Sub-Task ID component. This could lead to unauthorized access, data breaches, or the execution of malicious commands on the affected system. The vulnerability has a moderate severity rating and has been reviewed by GitHub. More details can be found in the GitHub Advisory Database.

How To Fix

Minimum fixed version

2.4.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to a patched version of xxl-job.

Conclusion

The vulnerability in xxl-job version 2.4.1 poses a risk of remote code execution due to insecure permissions. It is crucial for developers to upgrade to a patched version of xxl-job to mitigate this vulnerability and ensure the security of their applications.

See every vulnerability recorded for com.xuxueli:xxl-job-core →

Share this vulnerability

FAQ

xxl-job is a Maven package that provides job scheduling and task execution capabilities in Java applications.

The vulnerability allows a remote attacker to execute arbitrary code, potentially leading to unauthorized access, data breaches, or the execution of malicious commands.

To fix this vulnerability, it is recommended to upgrade to a patched version of xxl-job.

Currently, there is no known workaround for this vulnerability.

More information can be found in the GitHub Advisory Database.

Related vulnerabilities

Recent vulnerabilities recorded for com.xuxueli:xxl-job-core.

How To Fix

Minimum fixed version

2.4.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback