CVE-2019-15508· NVD / CVE Program· CNA mitre

In Octopus Tentacle versions 3.0.8 to 5.0.0, when a web request proxy is configured, an authenticated user (in certain limited OctopusPrintV

Noroxi assessment

Priority: Monitor (action score 26/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.66% (FIRST EPSS); higher than 51% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: n/a n/a 5.0.1.

Low priority for now. Upgrade to n/a n/a 5.0.1 or later.

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 Octopus Tentacle versions 3.0.8 to 5.0.0, when a web request proxy is configured, an authenticated user (in certain limited OctopusPrintVariables circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 5.0.1. The fix was back-ported to 4.0.7.

MediumCVSS 6.5 · v3.0—No exploit Fix available

Published: Aug 23, 2019
Updated: Jun 16, 2026
EPSS: 0.6% · 51th percentile
CWE: CWE-312

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

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	server	cpe:2.3:a:octopus:server
octopus	tentacle	cpe:2.3:a:octopus:tentacle

Affected versions

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

octopus server3.0.8 and later · up to 2019.7.6 inclusive
octopus tentacle3.0.8 and later · up to 5.0.0 inclusive

Same product

octopus: all records

Other highest-scoring records for the same primary product.

CVE-2021-31817When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written
30Monitor
CVE-2021-31816When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written
30Monitor
CVE-2021-30183Cleartext storage of sensitive information in multiple versions of Octopus Server where in certain situations when running import or export
30Monitor

Published before and after this one in the same product

← EarlierCVE-2019-15507Aug 23, 2019 · In Octopus Deploy versions 2018.8.4 to 2019.7.6, when a web request proxy is configured, an authenticated user (in certain limited special-c
26Monitor
Later →CVE-2019-19085Nov 18, 2019 · A persistent cross-site scripting (XSS) vulnerability in Octopus Server 3.4.0 through 2019.10.5 allows remote authenticated attackers to inj
21Monitor
Later →CVE-2021-31818Jun 17, 2021 · Affected versions of Octopus Server are prone to an authenticated SQL injection vulnerability in the Events REST API because user supplied d
17Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
n/a n/a	5.0.1 · description	Vendor (CNA)

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