CVE-2020-11009Network attack vector

Authenticated IDOR exposes execution data

Published Apr 29, 2020 · Updated Aug 4, 2024

Authorization bypass in PagerDuty Rundeck before 3.2.6 allows remote authenticated users to read restricted execution data via crafted requests. Rundeck API authorization checks fail to enforce required project, job, event, SCM, and user permissions on requests that return execution logs, job options, workflow details, and related metadata. Exploitation requires a valid authenticated account; impact is information disclosure whose severity depends on project permissions and whether sensitive secrets or intellectual property appear in execution output.

CVSS severity6.5
Medium
EPSS probability1.37%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in PagerDuty Rundeck before 3.2.6 allows remote authenticated users to read restricted execution data via crafted requests. Rundeck API authorization checks fail to enforce required project, job, event, SCM, and user permissions on requests that return execution logs, job options, workflow details, and related metadata. Exploitation requires a valid authenticated account; impact is information disclosure whose severity depends on project permissions and whether sensitive secrets or intellectual property appear in execution output.

The record

CVE
CVE-2020-11009
Published
Apr 29, 2020
Updated
Aug 4, 2024
Vendor
PagerDuty
Product
Rundeck
Classifications
CWE-639, CWE-200, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 29, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.2.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

PagerDuty · Rundeckversion=< 3.2.6

Published CVSS scores

6.5GitHub CNACVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0NVDAV:N/AC:L/Au:S/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 11, 2026Sep 17, 2026
Latest reporting daySep 17, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo