How severe is GHSA-wjjc-m3fc-fcm8?

GHSA-wjjc-m3fc-fcm8 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wjjc-m3fc-fcm8?

GHSA-wjjc-m3fc-fcm8 affects the following packages: moin (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-wjjc-m3fc-fcm8?

Update moin to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjjc-m3fc-fcm8 is resolved across your whole dependency graph.

How do I detect GHSA-wjjc-m3fc-fcm8 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wjjc-m3fc-fcm8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wjjc-m3fc-fcm8?

O3 pinpoints whether GHSA-wjjc-m3fc-fcm8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wjjc-m3fc-fcm8 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-wjjc-m3fc-fcm8, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

When was GHSA-wjjc-m3fc-fcm8 published, and has it been updated?

GHSA-wjjc-m3fc-fcm8 was published on May 17, 2022 and was last updated on November 26, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-wjjc-m3fc-fcm8

HIGH

GHSA-wjjc-m3fc-fcm8 is a high-severity (CVSS 7.5) vulnerability in moin. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-wjjc-m3fc-fcm8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MoinMoin Denial of Service vulnerability via password_checker function

Also known asCVE-2008-6549PYSEC-2009-12

Published

May 17, 2022

Updated

Nov 26, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐍moin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The password_checker function in config/multiconfig.py in MoinMoin prior to version 1.6.1 uses the cracklib and python-crack features even though they are not thread-safe, which allows remote attackers to cause a denial of service (segmentation fault and crash) via unknown vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`moin`	all versions	1.6.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The password_checker function in config/multiconfig.py in MoinMoin 1.6.1…

hg.moinmo.inNVDMar 2009

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update moin to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjjc-m3fc-fcm8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wjjc-m3fc-fcm8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wjjc-m3fc-fcm8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The password_checker function in `config/multiconfig.py` in MoinMoin prior to version 1.6.1 uses the cracklib and python-crack features even though they are not thread-safe, which allows remote attackers to cause a denial of service (segmentation fault and crash) via unknown vectors.

O3 Security · Impact-Aware SCA

Is GHSA-wjjc-m3fc-fcm8 in your dependencies?

O3 detects GHSA-wjjc-m3fc-fcm8 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works