CVE-2012-20008 json
openSIS 5.1 < 9.0 Authenticated Local File Inclusion via ajax.php modname
published 10h ago modified 9h ago also EUVD-2012-6618
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
openSIS 5.1 before 9.0 contains a local file inclusion vulnerability that allows authenticated users to include arbitrary files through the modname parameter of ajax.php. Attackers can prefix a payload with misc/ and use ../ directory traversal to read sensitive files like /etc/passwd or execute local scripts in the web server context. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.
Patch / fix
Is CVE-2012-20008 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploits and checks
- exploit-db.com https://www.exploit-db.com/exploits/38039 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- OS4ED openSIS
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
References
-
github.com
/OS4ED/openSIS-Classic/commit/a2d617977fa159185263845ac75b8c83cddd07f0
patch
-
exploit-db.com
/exploits/38039
exploit
-
github.com
/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensis-lfi.yaml
technical-description
-
vulncheck.com
/advisories/opensis-5.1-authenticated-local-file-inclusion-via-ajax-php-modname
third-party-advisory
-
vulncheck.com
/advisories/opensis-5.1-9.0-authenticated-local-file-inclusion-via-ajax-php-modname
third-party-advisory
Sources
- CVE List CVE-2012-20008
- NVD CVE-2012-20008
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.