CVE-2001-0229
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 · uneditedChili!Soft ASP for Linux before 3.6 does not properly set group privileges when running in inherited mode, which could allow attackers to gain privileges via malicious scripts.
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 confidenceChili!Soft ASP for Linux versions prior to 3.6 fail to properly set group privileges when running in inherited mode, allowing malicious ASP scripts to execute with elevated group permissions. This is a privilege escalation vulnerability where the application inherits incorrect group ownership or permissions during script execution.
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<= 3.6CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Confirm Chili!Soft ASP installationLocate the Chili!Soft ASP installation by searching for common installation directories such as /opt/chiliasp, /usr/local/chiliasp, or check the package manager for installed chilisoft or chiliasp packages.Affected if The software is not installed.
-
Identify installed versionRun the Chilisoft ASP version command if available, such as 'chasp -v' or check version files in the installation directory. Compare the version number against the affected range (versions prior to 3.6).Affected if The installed version is 3.6 or lower, or the version cannot be determined.
-
Determine if inherited mode is enabledExamine the Chili!Soft ASP configuration files (typically found in the config directory under the installation path) for settings related to 'inherited' mode or privilege inheritance. Look for configuration parameters that control how ASP scripts inherit user or group context.Affected if Inherited mode is enabled and the version is prior to 3.6.
-
Check running ASP process group contextUse commands such as 'ps aux | grep chili' or 'ps aux | grep casp' to identify running Chili!Soft ASP processes, then examine their group assignments using 'ps -eo pid,ppid,user,group,cmd' or similar process listing commands.Affected if The ASP processes are running with elevated group permissions that do not match expected secure configurations.
A system is affected if it runs Chili!Soft ASP version 3.6 or earlier with inherited mode enabled, where the application does not properly set group privileges during script execution.
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.
From vendor dataUpgrade Chili!Soft ASP to version 3.6 or later, which contains the fix for proper group privilege handling in inherited mode. If upgrading is not feasible, ensure that untrusted users cannot deploy or modify ASP scripts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0229 — 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-2001-0229 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