Security checks: Versions
Security checks: Versions
Section titled “Security checks: Versions”rConfig and operating system versions, compared with the advisory feed.
From V8.5.0, these checks run in php artisan rconfig:security-check and in Security Center. Run only this group with:
cd /var/www/html/rconfig8php artisan rconfig:security-check --only=versionsEach failing check shows the exact fix for your server, including paths, on the page and in the command output. The sections below explain what each check looks for.
| Check | Severity | Checks that |
|---|---|---|
versions.rconfig_latest |
High | rConfig is not behind a security release |
versions.os_eol |
High | The operating system still gets security updates |
rConfig is not behind a security release
Section titled “rConfig is not behind a security release”Check ID: versions.rconfig_latest · Severity: High
Many of rConfig’s security fixes are code changes that no setting can check, such as stored XSS or authorization fixes. Running the latest security release is the only way to have them.
References: NIST SI-2, NIS2 21(2)(e), CIS Controls 7.3
The operating system still gets security updates
Section titled “The operating system still gets security updates”Check ID: versions.os_eol · Severity: High
An end-of-life OS stops getting fixes for the kernel, OpenSSL, OpenSSH and every other package rConfig depends on.
References: NIST SI-2, NIS2 21(2)(e), CIS Controls 2.2
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.