dbcve.org
MoinmoinApplication · Moinmo

CVE-2010-0667

MEDIUM · 5.0 CVSS v2.0 Published 2010-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MoinMoin 1.9 before 1.9.1 does not perform the expected clearing of the sys.argv array in situations where the GATEWAY_INTERFACE environment variable is set, which allows remote attackers to obtain sensitive information via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

MoinMoin 1.9.x before 1.9.1 fails to clear the sys.argv array when the GATEWAY_INTERFACE environment variable is set, potentially exposing command-line arguments passed to the application to remote attackers.

MitigationUpgrade to MoinMoin 1.9.1 or later which implements proper sys.argv clearing when GATEWAY_INTERFACE is detected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MoinmoinApplication
Affected:= 1.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MoinMoin version
    Run 'python -c "import MoinMoin; print(MoinMoin.__version__)"' or check the version file in the MoinMoin installation directory
    Affected if The installed version is 1.9.0 (the only explicitly vulnerable version listed)
  2. Verify CGI environment configuration
    Check if the GATEWAY_INTERFACE environment variable is set on the server running MoinMoin. Run 'echo $GATEWAY_INTERFACE' in the web server environment or inspect CGI/WSGI configuration files
    Affected if GATEWAY_INTERFACE is set (typically to 'CGI/1.1' for CGI deployments) - this is the condition that triggers the vulnerable code path
  3. Inspect sys.argv exposure
    In a test CGI request, examine whether application command-line arguments (such as those used in server startup) are visible in the application or accessible via debugging/error output
    Affected if Command-line arguments passed to the MoinMoin process are visible or retrievable through the web application interface

A user is affected if running MoinMoin version 1.9.0 in a CGI context where GATEWAY_INTERFACE is set, and command-line arguments become exposed to remote attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to MoinMoin 1.9.1 or later which implements proper sys.argv clearing when GATEWAY_INTERFACE is detected.

Fix this in Moinmoin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0667 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data