Skip to content

GHSA-876c-qmcf-cxv6 CVE-2010-0667 PYSEC-2010-14

MoinMoin Exposure of Sensitive Disclosure when GATEWAY_INTERFACE variable is set

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
1.87%
Chance of exploitation in the next 30 days. Higher than 79.34% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.9.1
Upgrade moin to this version or later

Description

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.

Affected versions

PyPI

PackageVulnerableFixed in
moin
>= 1.9, < 1.9.1
1.9.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

moin PyPI → 1.9.1

pip
pip install --upgrade "moin>=1.9.1"
poetry
poetry add "moin>=1.9.1"
uv
uv add "moin>=1.9.1"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-cx94-3h5x-cc57
MoinMoin Cross-site scripting (XSS) vulnerability in the antispam feature
Medium Also affects moin
GHSA-7hjm-hqgj-xv9f
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-jj2f-57jg-5rm6
MoinMoin Improper Access Control
Medium Also affects moin
GHSA-8fj9-pj4p-4vq7
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-6766-r2rx-mfw9
MoinMoin Directory traversal vulnerability
Medium Also affects moin
GHSA-775g-4482-pm94
MoinMoin Multiple cross-site scripting (XSS) vulnerabilities
Medium Also affects moin
GHSA-53wj-6m7w-j6mj
MoinMoin Cross-site scripting (XSS) vulnerability
Medium Also affects moin
GHSA-cmg7-xr2j-4r9v
MoinMoin Improper ACL handling for calendars and includes
Medium Also affects moin
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor