In affected versions of Octopus Server it is possible to reveal information about teams via the API due to an Insecure Direct Object Referen

Affected versions

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

• octopus octopus server2022.1.2121 and later · up to 2022.1.3135 inclusive
• octopus octopus server2022.2.0 and later · up to 2022.2.7897 inclusive
• octopus octopus server2022.3.0 and later · up to 2022.3.10586 inclusive

Versions reported by the vendor

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

• Octopus Deploy Octopus Server

  • 2022.1.2121 and later · before unspecifiedaffected
  • unspecified and later · before 2022.1.3135affected
  • 2022.2.6729 and later · before unspecifiedaffected
  • unspecified and later · before 2022.2.7897affected
  • 2022.3.348 and later · before unspecifiedaffected
  • unspecified and later · before 2022.3.10586affected

Other highest-scoring records for the same primary product.

• CVE-2022-2572In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys
  39Monitor
• CVE-2022-2778In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes.
  39Monitor
• CVE-2018-18850In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could uplo
  39Monitor
• CVE-2018-11320In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in t
  39Monitor
• CVE-2022-2782In affected versions of Octopus Server it is possible for a session token to be valid indefinitely due to improper validation of the session
  36Monitor
• CVE-2022-4009In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation
  35Monitor

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.