This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-31129 →

UBUNTU-CVE-2022-31129

Vulnerability in gnucash (UBUNTU-CVE-2022-31129)

Summary

Vulnerability in gnucash (UBUNTU-CVE-2022-31129). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.29.4 or later.

Original description

The description as published by the source.

moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2022-31129 has been found in gnucash.
Risk of unauthorized operations or information disclosure.
What to do: upgrade gnucash to 2.29.4 or later.
If unsure, ask your IT team or search "gnucash UBUNTU-CVE-2022-31129" on the vendor's site.

UBUNTU-CVE-2022-31129 (gnucash)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.29.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.

❓ What is the problem

A vulnerability (unclassified) exists in gnucash.

📍 Affected scope

Check the vendor advisory for the affected versions of gnucash.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.29.4.

🛡️ 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 'gnucash' . 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 exposure identify
```
grep -r 'gnucash' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gnucash を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade gnucash to 2.29.4
```
ステージング環境で 2.29.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。