CVE-2004-2611: The Change Permissions function in the Sophster suite before 0.9.6 28 May 2004 (aka 0.9.6-r5), possibly includ
CVE-2004-2611 is a medium-severity flaw (CVSS 4.6) affecting sophster. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Change Permissions function in the Sophster suite before 0.9.6 28 May 2004 (aka 0.9.6-r5), possibly including Sophster, FreeSophster, and FreeSophsterPAM, removes the (1) setuid, (2) setgid, and (3) sticky bits when changing a file, which might allow attackers to gain privileges or conduct other unauthorized activities.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 4.6 (Medium) |
| EPSS exploit chance | 0.3% (top 71%) |
| CISA exploited list | No |
| Published | 2004-12-31 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2004-2611?
sophster: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2004-2611 being exploited?
CVE-2004-2611 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2004-2611 affect?
CVE-2004-2611 affects sophster. Severity is medium (CVSS 4.6). The Change Permissions function in the Sophster suite before 0.9.6 28 May 2004 (aka 0.9.6-r5), possibly including Sophster, FreeSophster, and FreeSophsterPAM, removes the (1) setuid, (2) setgid, and (3) sticky bits when changing a file, whi
How urgent is CVE-2004-2611?
Priority 23/100. No elevated risk signals yet.