CVE-2022-3460· NVD / CVE Program· CNA Octopus

In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview.

HighCVSS 7.5 · v3.1—No exploit No fix recorded

Pre-auth

Published: Jan 2, 2023
Updated: Jun 17, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-212

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
octopus	octopus server	cpe:2.3:a:octopus:octopus_server

Affected versions

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

octopus octopus server2018.1.0 and later · before 2022.3.10750
octopus octopus server2022.4 and later · before 2022.4.8063

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
- 2018.3.1 and later · before unspecifiedaffected
- unspecified and later · before 2021.3.13150affected
- 2022.1.2121 and later · before unspecifiedaffected
- unspecified and later · before 2022.1.3281affected
- 2022.2.7897 and later · before unspecifiedaffected
- unspecified and later · before 2022.2.8552affected
- 2022.3.348 and later · before unspecifiedaffected
- unspecified and later · before 2022.3.10750affected
- 2022.4.791 and later · before unspecifiedaffected
- unspecified and later · before 2022.4.8221affected

Same product

octopus: all records

Other highest-scoring records for the same primary product.

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
40Plan
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

Published before and after this one in the same product

← EarlierCVE-2022-2782Oct 27, 2022 · In affected versions of Octopus Server it is possible for a session token to be valid indefinitely due to improper validation of the session
36Monitor
← EarlierCVE-2022-2721Nov 25, 2022 · In affected versions of Octopus Server it is possible for target discovery to print certain values marked as sensitive to log files in plain
30Monitor
Later →CVE-2022-3614Jan 2, 2023 · In affected versions of Octopus Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication ch
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

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

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope