Skip to content

GHSA-6278-2q4m-cmf3 CVE-2022-36537

ZK Framework vulnerable to malicious POST

High Known exploited Maven
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
95.40%
Chance of exploitation in the next 30 days. Higher than 99.87% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Feb 27, 2023
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
8.6.4.2
Upgrade org.zkoss.zk:zk to this version or later
Exploited in the wild. ZK Framework AuUploader Unspecified Vulnerability (ZK Framework AuUploader). Required action: Apply updates per vendor instructions. Due for U.S. federal agencies by Mar 20, 2023. Known to be used in ransomware campaigns.

Description

ZK Framework version 9.6.1, 9.6.0.1, 9.5.1.3, 9.0.1.2 and 8.6.4.1 allows attackers to access sensitive information via a crafted POST request sent to the component AuUploader.

Affected versions

Maven

PackageVulnerableFixed in
org.zkoss.zk:zk
< 8.6.4.2
8.6.4.2
org.zkoss.zk:zk
>= 9.0.0.0, < 9.0.1.3
9.0.1.3
org.zkoss.zk:zk
>= 9.5.0.0, < 9.5.1.4
9.5.1.4
org.zkoss.zk:zk
>= 9.6.0.0, < 9.6.0.2
9.6.0.2
org.zkoss.zk:zk
>= 9.6.1, < 9.6.2
9.6.2
org.zkoss.zk:zk
< 8.6.4.2
8.6.4.2
org.zkoss.zk:zk
>= 9.0.0.0, < 9.0.1.3
9.0.1.3
org.zkoss.zk:zk
>= 9.5.0.0, < 9.5.1.4
9.5.1.4
org.zkoss.zk:zk
>= 9.6.0.0, < 9.6.0.2
9.6.0.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.zkoss.zk:zk Maven → 8.6.4.2

maven
<dependency><groupId>org.zkoss.zk</groupId><artifactId>zk</artifactId><version>8.6.4.2</version></dependency>
gradle
implementation("org.zkoss.zk:zk:8.6.4.2")

Severity breakdown

CVSS 3.1 7.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Exploit maturity
H

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-j7qq-vr8c-xvw3
MLflow CrewAI autologging records LLM provider API keys in logged trace spans
Medium Same weakness, CWE-200
GHSA-gqh3-7856-rjjg
ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthenticated doc-existence + locale metadata disclosure)
Medium Same weakness, CWE-200
GHSA-rqgm-cfrp-4hx8
ApostropheCMS: Unauthenticated publicApiProjection bypass via search and sort query builders in the public REST API
Medium Same weakness, CWE-200
GHSA-f66c-mpj2-3r8h
ApostropheCMS: POST /api/v1/@apostrophecms/doc/slugTaken discloses existence of private/admin-only content to any authenticated user
Medium Same weakness, CWE-200
GHSA-vfpm-58rq-9qcg
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
Medium Same weakness, CWE-200
GHSA-23mf-xhv8-69c2
GitPython: arbitrary file read via attacker-controlled branch name in `Head.checkout()` (incomplete fix of CVE-2026-78679)
High Same weakness, CWE-200
GHSA-fx3j-rwgx-fr94
GitPython: separate_git_dir leaks env vars via crafted .gitmodules submodule name
High Same weakness, CWE-200
GHSA-vp88-798v-h67f
rustls: ECH rejection can expose buffered application data to authenticated outer server before `ech_required` alert
Low Same weakness, CWE-200

Credits: tdunlap607

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor