← Back
GHSA-3m6q-h5gj-7mrw
Vulnerability in code.gitea.io/gitea (GHSA-3m6q-h5gj-7mrw)
Summary
vulnerability in code.gitea.io/gitea (GHSA-3m6q-h5gj-7mrw). Risk of unauthorized operations or information disclosure. Exploitable via ``fail``. Mitigation: upgrade to `1.25.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-3m6q-h5gj-7mrw** has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like ``fail`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade code.gitea.io/gitea to **1.25.0** or later.
If unsure, ask your IT team or search "code.gitea.io/gitea GHSA-3m6q-h5gj-7mrw" on the vendor's site.
GHSA-3m6q-h5gj-7mrw (code.gitea.io/gitea) — CWE-1188 /
Attack surface: `fail` / `SSH_SERVER_KEY_EXCHANGES` / `SSH_SERVER_CIPHERS` / `SSH_SERVER_MACS`
Patched: `1.25.0` — 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-1188) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via ``fail`` without authentication.
📍 Affected scope
code.gitea.io/gitea — . Attack surface: `fail` / `SSH_SERVER_KEY_EXCHANGES` / `SSH_SERVER_CIPHERS` / `SSH_SERVER_MACS`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.25.0**.
🛡️ 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 'code.gitea.io/gitea' .` 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 'code.gitea.io/gitea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `code.gitea.io/gitea` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade code.gitea.io/gitea to 1.25.0ステージング環境で 1.25.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
code.gitea.io/gitea
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.25.0"}]}]