Vulnerability in github.com/siyuan-note/siyuan/kernel (GHSA-75xh-mp4f-f2rf)
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
A vulnerability tracked as GHSA-75xh-mp4f-f2rf has been found in github.com/siyuan-note/siyuan/kernel.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 3.7.4 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel GHSA-75xh-mp4f-f2rf" on the vendor's site.
GHSA-75xh-mp4f-f2rf (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.7.4 — 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.
A vulnerability (CWE-862) exists in github.com/siyuan-note/siyuan/kernel.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 3.7.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/siyuan-note/siyuan/kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'github.com/siyuan-note/siyuan/kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/siyuan-note/siyuan/kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade github.com/siyuan-note/siyuan/kernel to 3.7.4ステージング環境で 3.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| gogithub.com/siyuan-note/siyuan/kernel |
≥ 0.0.0-20260726161145-9b8e8956f997, < 0.0.0-20260812083335-251596fc0de2→ 0.0.0-20260812083335-251596fc0de2 |
0.0.0-20260812083335-251596fc0de2 |
| siyuan-notesiyuan |
≥ 3.7.4-alpha.2, < 3.7.4-alpha.3→ 3.7.4-alpha.3 |
3.7.4-alpha.3 |
Original description The description as published by the source.
SiYuan's development branch (endpoint introduced by commit 9b8e8956f, not present in v3.7.3 or master, patched in v3.7.4-alpha.3) contains a missing-authorization vulnerability in the /api/av/getAttributeViewSearchTarget endpoint. The route is registered with CheckAuth only and performs no authorization checks (no CheckReadonly, no publish-access or encrypted-notebook gating). Given a database identifier taken from a published page and a keyword, an anonymous reader can query the endpoint to retrieve matching database row content, including rows that publish filters (FilterAttributeViewByPublishAccess) would otherwise withhold. No released stable version is affected.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com