CVE-2000-0352
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 · uneditedPine before version 4.21 does not properly filter shell metacharacters from URLs, which allows remote attackers to execute arbitrary commands via a malformed URL.
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 · high confidencePine email client versions prior to 4.21 fail to properly filter shell metacharacters embedded in URLs. When a user clicks or processes a maliciously crafted URL, the unfiltered metacharacters can be interpreted by the shell, allowing arbitrary command execution on the affected system.
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= 4.20= 4.21CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Pine is installedLocate the Pine binary on the system using 'which pine' or by searching common binary directoriesAffected if Pine executable is found on the system
-
Determine installed Pine versionRun 'pine -version' or 'pine --version' to display the version numberAffected if The displayed version is 4.20 or earlier
-
Confirm version matches affected rangeCompare the installed version number to the affected range (versions prior to 4.21)Affected if The version is 4.20 or any version lower than 4.21
-
Identify URL handling usageCheck if Pine is configured for email processing where users may click or open embedded URLsAffected if Pine is used to read email containing clickable URLs, as the flaw requires user interaction with a malicious URL
A system is affected if Pine version 4.20 or earlier is installed and users process emails with embedded URLs that could contain shell metacharacters.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Pine to version 4.21 or later to obtain the patched version that properly sanitizes URL input. Users should avoid clicking untrusted or suspicious URLs until the upgrade is applied.
Pine 4.21 or later (note: Pine has been discontinued since 2005; consider migrating to Alpine or another actively maintained email client)
- 1. Check the current Pine version by running 'pine -v' or 'pine -version'
- 2. Verify the operating system and package management system in use (e.g., RPM for Linux, or source compilation)
- 3. Obtain Pine version 4.21 or later from a trusted source such as the distribution's official repositories or archived software repositories
- 4. Back up any important Pine configuration files (typically located in ~/.pinerc or /etc/pine.conf)
- 5. Install the updated Pine package using the appropriate package manager (e.g., 'rpm -Uvh pine-4.21.rpm' for RPM-based systems)
- 6. Verify the new version is installed by running 'pine -v' again
- 7. Review the configuration files to ensure no malicious modifications were made during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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