Vulnerabilities · 2020 · Froxlor
CVE-2020-10236
Froxlor vulnerability
An issue was discovered in Froxlor before 0.10.14. It created files with static names in /tmp during installation if the installation directory was not writable. This allowed local attackers to cause DoS or disclose information out of the config files, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.
Affected products
Froxlor. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Froxlor runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/Froxlor/Froxlor/commit/6b09720ef8a1cc008751dd0ca0140a0597fedce5 · Patch
- github.com/Froxlor/Froxlor/compare/0.10.13...0.10.14 · Patch
- bugzilla.suse.com/show_bug.cgi?id=1165718 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-10236
- github.com/advisories/GHSA-hvgf-2rf7-wrx9
- nvd.nist.gov/vuln/detail/CVE-2020-10236
- cve.org/CVERecord?id=CVE-2020-10236
More vulnerabilities in Froxlor products
CVE-2025-48958CVE-2025-29773CVE-2023-50256CVE-2023-6069CVE-2023-5564CVE-2023-4829CVE-2023-4304CVE-2023-3668All 39
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.