LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40082: Hertz v0.3.0 ws discovered to contain a path traversal vulnerability via the normalizePath function.

Hertz v0.3.0 ws discovered to contain a path traversal vulnerability via the normalizePath function.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-40082 is a path traversal flaw reported in Hertz v0.3.0 ws path normalization. If exposed in a deployed service, an unauthenticated remote user could potentially read files the service can access. The source bundle does not identify broad affected product metadata or a fixed release version.

Executive priority

Treat as high priority for internet-facing services using Hertz v0.3.0. The main business risk is unauthorized disclosure of sensitive files, not service takeover. Prioritize inventory first because affected-product metadata is incomplete in the CVE bundle.

Technical view

The issue is mapped to CWE-22 and attributed to Hertz v0.3.0 ws normalizePath handling. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, with high confidentiality impact only. Public references are a GitHub issue and pull request, but the bundle does not include exploit details or fixed-version metadata.

Likely exposure

Likely exposure is limited to services using Hertz v0.3.0 ws code paths affected by normalizePath. Internet-facing deployments are higher priority. Dependency manifests and runtime routes should be checked because the CVE affected metadata lists no concrete CPEs or vendor/product identifiers.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated exploitability with confidentiality impact, but no public exploit status or attack prevalence is provided here.

Researcher notes

Evidence is sparse: the CVE names Hertz v0.3.0 ws and normalizePath, assigns CWE-22, and references GitHub issue #228 and PR #229. Do not infer affected versions beyond the stated version without checking upstream project history and release notes.

Mitigation direction

  • Check CloudWeGo Hertz guidance, issue #228, and pull request #229 for the vendor-corrected fix.
  • Upgrade away from Hertz v0.3.0 if the vendor identifies a fixed release.
  • Restrict public access to affected ws routes until remediation is confirmed.
  • Review service file access permissions to limit sensitive file exposure impact.

Validation and detection

  • Inventory applications and containers for Hertz v0.3.0 dependency usage.
  • Confirm whether ws routes use normalizePath-related file handling.
  • Review access logs for suspicious traversal-like path patterns around exposed endpoints.
  • Verify the deployed dependency includes the upstream correction referenced by PR #229.
Prepared
Confidence
medium
Sources
4

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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.

Open ATT&CK lookup
description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-40082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-40082Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.