CVE-2020-10237
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 · uneditedAn issue was discovered in Froxlor through 0.10.15. The installer wrote configuration parameters including passwords into files in /tmp, setting proper permissions only after writing the sensitive data. A local attacker could have disclosed the information if he read the file at the right time, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.
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 confidenceIn Froxlor through 0.10.15, the installer writes configuration parameters including passwords to files in /tmp before setting proper file permissions. This creates a Time-of-Check to Time-of-Use (TOCTOU) race condition where a local attacker with read access to /tmp could intercept sensitive credentials during the window before permissions are restricted.
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<= 0.10.15CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Froxlor versionLocate the Froxlor installation directory and find the version file, typically in a file named 'version' or within the main Froxlor PHP files. Common paths include /var/www/froxlor or /usr/share/froxlor. Alternatively, check the database if accessible for version information.Affected if The installed version is 0.10.15 or lower.
-
Determine if installation was performedCheck for the presence of the install directory (install/) and whether the configuration file (like userdata.conf) exists in /tmp or the Froxlor config directory. On Linux, run: ls -la /tmp | grep -i froxlor or check the documented config path.Affected if The installation has been run and the vulnerable code path was executed.
-
Inspect the installation source for the vulnerabilityIf the install source is accessible, locate install/lib/class.FroxlorInstall.php and examine the _createUserdataConf function. Look for whether chmod is called before or after file writing. Search for the pattern: file_put_contents followed by chmod, which indicates the vulnerable order.Affected if The code writes sensitive data to the file before calling chmod, creating the TOCTOU window.
-
Check for leftover sensitive files in /tmpRun: ls -la /tmp/*froxlor* or ls -la /tmp/*userdata* to look for any configuration files that may have been created during installation and not cleaned up. Also check for any world-readable files containing passwords.Affected if Any Froxlor configuration files with passwords exist in /tmp with permissive permissions.
You are affected if your Froxlor version is 0.10.15 or lower and the installation was performed using the vulnerable code path, since the race condition occurs during the initial setup phase.
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 dataThe fix requires modifying the _createUserdataConf function in install/lib/class.FroxlorInstall.php to set restrictive file permissions (e.g., chmod 0600) before writing sensitive data, or use atomic file creation methods that set permissions atomically.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.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-2020-10237 — 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-2020-10237 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