CVE-2021-41112
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRundeck is an open source automation service with a web console, command line tools and a WebAPI. In versions prior to 3.4.5, authenticated users could craft a request to modify or delete System or Project level Calendars, without appropriate authorization. Modifying or removing calendars could cause Scheduled Jobs to execute, or not execute on desired calendar days. Severity depends on trust level of authenticated users and impact of running or not running scheduled jobs on days governed by calendar definitions. Version 3.4.5 contains a patch for this issue. There are currently no known workarounds.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRundeck versions prior to 3.4.5 contain an authorization bypass vulnerability where authenticated users can modify or delete System or Project level Calendars without proper authorization. This broken access control allows users to alter calendar definitions that control when scheduled jobs execute, potentially causing jobs to run or be suppressed on incorrect dates.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.4.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Rundeck versionLocate and inspect the Rundeck application version information - typically available in the UI footer, startup logs, or administration panelAffected if Version is below 3.4.5 (any 3.x version prior to 3.4.5, or any earlier major version)
-
Check for System-level CalendarsNavigate to System Menu > System Calendars or equivalent configuration area in the Rundeck administration interfaceAffected if Any System-level Calendar definitions exist in the environment
-
Check for Project-level CalendarsNavigate to individual Project settings and locate the Calendars configuration section for any projectAffected if Any Project-level Calendar definitions exist in one or more projects
-
Verify Calendar authorization controlsAttempt to access calendar modification functions with a non-administrator authenticated user account - check if users without admin privileges can view, edit, or delete calendar configurationsAffected if Non-administrator users can modify or delete System or Project calendars without receiving authorization errors
Environment is affected if running Rundeck version prior to 3.4.5 AND at least one System or Project calendar is configured, regardless of user role permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.4.5
Upgrade to Rundeck version 3.4.5 or later to apply the patch. No workarounds exist; immediate patching is recommended given the CVSS 8.1 severity and potential for disrupting scheduled job execution.
3.4.5
- Review the official Rundeck upgrade documentation for your installation method (Docker, RPM, DEB, or ZIP)
- Ensure you have a complete backup of your Rundeck data including the database and configuration files
- Stop the Rundeck service before upgrading
- Upgrade to version 3.4.5 or later using your package manager or by replacing the installation files
- Verify the upgrade was successful by checking the Rundeck version in the web UI or via CLI
- Start the Rundeck service and verify normal operation
- Review and test scheduled jobs to ensure calendars are functioning correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-41112 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data