goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.
Security readout for executives and security teams
Plain-English summary
goshs versions before 2.1.4 can violate the promised no-deletion safeguard. A remote WebDAV client may move files in a way that deletes the original or overwrites another file, potentially disrupting services or corrupting data. The issue affects integrity and availability, not confidentiality according to the supplied CVSS assessment.
Executive priority
Act urgently on externally reachable or operationally important goshs deployments. Upgrade affected instances promptly and examine file integrity where --no-delete was trusted. The critical score reflects straightforward remote corruption or deletion potential, but current sources do not establish exploitation in the wild.
Technical view
The wdGuard logic treated WebDAV MOVE as write-only and failed to apply --no-delete protections. A network client requiring no privileges or user interaction could use MOVE with overwrite behavior to remove a source file or replace a destination. CVSS 3.1 rates it 9.1, with high integrity and availability impact.
Likely exposure
Exposure is limited to goshs versions earlier than 2.1.4 where WebDAV is network-accessible, especially deployments relying on --no-delete to protect hosted files. The supplied sources do not quantify internet-facing installations or confirm whether additional deployment controls reduce reachability.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation without privileges or user interaction. However, the source bundle reports no CISA KEV listing and provides no evidence of active exploitation, public weaponization, or observed attacks. Treat exploitation status as unconfirmed.
Researcher notes
This is an authorization-control failure classified as CWE-284. The security boundary failed because MOVE changes both source and destination state, while the guard modeled it only as a write operation. The referenced fix commit and 2.1.4 release support remediation, but the supplied evidence does not establish exploit prevalence or affected deployment counts.
Mitigation direction
Upgrade goshs to version 2.1.4 or later.
Prioritize network-reachable instances using --no-delete.
Restrict untrusted network access until affected instances are upgraded.
Confirm recoverable backups exist for files served by affected systems.
Consult the vendor advisory and release notes before restoring normal exposure.
Validation and detection
Inventory goshs deployments and record their exact versions.
Identify instances earlier than 2.1.4 using --no-delete.
Confirm upgraded systems report version 2.1.4 or later.
Review HTTP or WebDAV logs for unexpected MOVE requests.
Check protected directories for unexplained deletions or overwritten files.
Safely verify that no-delete policy blocks MOVE-related deletion after upgrading.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.