CVE-2018-16367: In OnlineJudge 2.0, the sandbox has an incorrect access control vulnerability that can write a file anywhere
CVE-2018-16367 is a critical-severity flaw (CVSS 9.9) affecting onlinejudge. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In OnlineJudge 2.0, the sandbox has an incorrect access control vulnerability that can write a file anywhere. A user can write a directory listing to /tmp, and can leak file data with a #include.
Why this priority
- Critical severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.9 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 2.2% (top 18%) |
| CISA exploited list | No |
| Weakness | CWE-22 |
| Published | 2018-09-02 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · 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-2018-16367?
onlinejudge: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-16367 being exploited?
CVE-2018-16367 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-2018-16367 affect?
CVE-2018-16367 affects onlinejudge. Severity is critical (CVSS 9.9). In OnlineJudge 2.0, the sandbox has an incorrect access control vulnerability that can write a file anywhere. A user can write a directory listing to /tmp, and can leak file data with a #include.
How urgent is CVE-2018-16367?
Priority 60/100. Critical severity; Public exploit reference