Security readout for executives and security teams
Plain-English summary
gowitness versions before 2.3.6 could let an unauthenticated person request a screenshot of a local file by using a file:// URL. If a vulnerable gowitness service is reachable by untrusted users, sensitive files readable by the gowitness process could be exposed as images.
Executive priority
Treat internet-facing or shared gowitness deployments as urgent because the issue can expose local files without authentication. Local-only, tightly restricted instances are lower priority but should still be updated.
Technical view
The CVE describes arbitrary file read in gowitness < 2.3.6 through the url parameter accepting the file:// scheme. The issue is unauthenticated and results in an image of a local file. No CVSS, CWE, or vendor-structured affected product data is provided in the bundle.
Likely exposure
Exposure is limited to deployments running gowitness before 2.3.6 where its URL screenshot functionality is accessible to untrusted users or networks. The bundle does not state whether gowitness is exposed by default.
Exploitation context
The CVE source says unauthenticated exploitation is possible through the url parameter. The bundle does not provide evidence of active exploitation, and KEV status is false. Public disclosure references exist, but exploit maturity is not established here.
Researcher notes
The source data is sparse: no CVSS vector, CWE, CPE, or detailed advisory text is included. Analysis relies on the CVE description and the 2.3.6 release reference. Do not infer affected forks, defaults, or broader product impact.
Mitigation direction
- Inventory gowitness deployments and confirm their versions.
- Upgrade gowitness to 2.3.6 or later where applicable.
- Restrict gowitness access to trusted administrators and networks.
- Check vendor release notes for any additional hardening guidance.
- Review local files and secrets accessible to the gowitness process.
Validation and detection
- Confirm no deployed gowitness version is below 2.3.6.
- Verify public and untrusted networks cannot reach gowitness services.
- Review application logs for suspicious file:// URL submissions.
- Check host-level permissions for files readable by the gowitness process.
- Confirm remediation with security testing that avoids exposing sensitive file contents.
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-2021-33359 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://twitter.com/leonjza/status/1395283512433971202?s=19CVE reference · x_refsource_MISC
- https://github.com/sensepost/gowitness/releases/tag/2.3.6CVE reference · x_refsource_MISC
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.