← Back
CVE-2022-39366
Vulnerability in acryl-datahub (CVE-2022-39366)
Summary
vulnerability in acryl-datahub (CVE-2022-39366). Data can be tampered with by attackers. Exploitable via ``StatelessTokenService``. Mitigation: upgrade to `0.8.45` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-39366** has been found in acryl-datahub.
Attackers can target a specific entry point like ``StatelessTokenService`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade acryl-datahub to **0.8.45** or later.
If unsure, ask your IT team or search "acryl-datahub CVE-2022-39366" on the vendor's site.
CVE-2022-39366 (acryl-datahub) — CWE-347 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `StatelessTokenService` / `parse`
Patched: `0.8.45` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-347) exists in acryl-datahub. Attackers reach the vulnerable code path via ``StatelessTokenService`` without authentication.
📍 Affected scope
acryl-datahub — . Attack surface: `StatelessTokenService` / `parse`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **0.8.45**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'acryl-datahub' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'acryl-datahub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `acryl-datahub` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade acryl-datahub to 0.8.45ステージング環境で 0.8.45 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
acryl-datahub
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.45"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-39366
- advisory https://github.com/advisories/GHSA-r8gm-v65f-c973
- package https://github.com/datahub-project/datahub
- package https://pypi.org/project/acryl-datahub
- web https://github.com/datahub-project/datahub/security/advisories/GHSA-r8gm-v65f-c973
- web https://codeql.github.com/codeql-query-help/java/java-missing-jwt-signature-check
- web https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L134
- web https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L30
- web https://github.com/datahub-project/datahub/releases/tag/v0.8.45