{"api_version":"1","generated_at":"2026-07-23T10:04:34+00:00","cve":"CVE-2019-15508","urls":{"html":"https://cve.report/CVE-2019-15508","api":"https://cve.report/api/cve/CVE-2019-15508.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-15508","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-15508"},"summary":{"title":"CVE-2019-15508","description":"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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-08-23 06:15:00","updated_at":"2022-07-27 17:20:00"},"problem_types":["CWE-532","CWE-312"],"metrics":[],"references":[{"url":"https://github.com/OctopusDeploy/Issues/issues/5750","name":"https://github.com/OctopusDeploy/Issues/issues/5750","refsource":"MISC","tags":["Issue Tracking","Third Party Advisory"],"title":"Tentacle TentacleProxyPassword logged in clear text when OctopusPrintVariables is set · Issue #5750 · OctopusDeploy/Issues · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-15508","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-15508","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"15508","vulnerable":"1","versionEndIncluding":"2019.7.6","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"octopus","cpe5":"server","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"15508","vulnerable":"1","versionEndIncluding":"5.0.0","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"octopus","cpe5":"tentacle","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-15508","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://github.com/OctopusDeploy/Issues/issues/5750","refsource":"MISC","name":"https://github.com/OctopusDeploy/Issues/issues/5750"}]}},"nvd":{"publishedDate":"2019-08-23 06:15:00","lastModifiedDate":"2022-07-27 17:20:00","problem_types":["CWE-532","CWE-312"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.8,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:S/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":3.5},"severity":"LOW","exploitabilityScore":6.8,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:octopus:server:*:*:*:*:*:*:*:*","versionStartIncluding":"3.0.8","versionEndIncluding":"2019.7.6","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:octopus:tentacle:*:*:*:*:*:*:*:*","versionStartIncluding":"3.0.8","versionEndIncluding":"5.0.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"15508","Ordinal":"154993","Title":"CVE-2019-15508","CVE":"CVE-2019-15508","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"15508","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"15508","Ordinal":"2","NoteData":"2019-08-23","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"15508","Ordinal":"3","NoteData":"2019-08-23","Type":"Other","Title":"Modified"}]}}}