Security readout for executives and security teams
Plain-English summary
Octopus Deploy 3.x before 3.15.4 allowed a user with package upload rights to craft a NuGet package name that could write outside the intended package area. This could overwrite packages or modify system files. The issue requires authentication and PackagePush permission, but affected deployment infrastructure can be business-critical.
Executive priority
Prioritize remediation for any affected Octopus server connected to production deployment pipelines. The issue is permission-gated, but compromise or misuse of a package-publishing account could affect deployment artifacts or server files.
Technical view
The vulnerability is a directory traversal in the NuGet PackageId value used during package upload handling. An authenticated principal with PackagePush permission could submit a crafted package that writes to unintended paths, potentially overwriting packages or modifying system files. The provided CVE data names Octopus Deploy 3.x before 3.15.4.
Likely exposure
Exposure is likely limited to Octopus Deploy 3.x servers older than 3.15.4 where users, service accounts, or CI systems have PackagePush permission. Public internet exposure is not stated in the sources.
Exploitation context
The sources do not report active exploitation, public exploit use, or CISA KEV listing. Abuse requires valid access with PackagePush permission. Impact depends on Octopus server file permissions and what paths package processing could reach.
Researcher notes
The bundle lacks CVSS, CWE, detailed affected CPEs, and exploit telemetry. Analysis is based on the CVE description and Octopus issue reference. Avoid assuming code execution or broader product impact without vendor evidence.
Mitigation direction
- Upgrade Octopus Deploy 3.x instances to 3.15.4 or later.
- Restrict PackagePush permission to trusted users and automation accounts.
- Review service account credentials used by CI package publishing workflows.
- Check Octopus vendor guidance for any additional hardening recommendations.
- Monitor package storage and server file integrity for unexpected changes.
Validation and detection
- Inventory Octopus Deploy servers and record exact version numbers.
- Confirm no production server runs Octopus Deploy 3.x before 3.15.4.
- Review users, teams, API keys, and service accounts with PackagePush permission.
- Inspect package audit history for unusual package IDs or unexpected overwrites.
- Check server logs and file integrity records around package upload events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-11348 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OctopusDeploy/Issues/issues/3654CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.