Authorization Bypass Through User-Controlled Key in Rundeck

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• pagerduty rundeckbefore 3.3.15
• pagerduty rundeck3.4.0 and later · before 3.4.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• rundeck rundeck

  • < 3.3.15, >= 3.4.0, < 3.4.5affected

Other highest-scoring records for the same primary product.

• CVE-2022-29186Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise
  39Monitor
• CVE-2021-39132YAML deserialization can run untrusted code
  36Monitor
• CVE-2021-41112Missing Authorization in Rundeck
  32Monitor
• CVE-2022-31044Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation
  30Monitor
• CVE-2021-39133Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server
  27Monitor
• CVE-2020-11009IDOR can reveal execution data and logs to unauthorized user in Rundeck
  26Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const invoice = await Invoice.findById(req.params.id);2res.json(invoice);

1const invoice = await Invoice.findOne({2  id: req.params.id,3  ownerId: req.user.id,4});5if (!invoice) return res.sendStatus(404);6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.