CWP 1.30.14 (LTS) - changes since 1.30.13
Fixes
Security:
- OAuth authorize endpoint now fails closed for unidentifiable callers. The internal endpoint that issues OAuth
authorization codes identifies the local caller by the uid that owns its connection, so only an account's own user
panel or a system service can obtain a code for that account. When it could not read the kernel connection table to
identify the caller it previously allowed the request; it now denies it. It also reads the connection table directly
when possible, so pools with exec disabled keep working without weakening the check.
- OAuth client secrets now use a cryptographically secure random generator. The per-account OAuth client secret (used
by the internal API) was previously generated in several code paths from a small, time-seeded value. Every place
that creates an OAuth client now uses a cryptographically secure generator, and after this update each server rotates
every existing account's stored client secret once (an automatic, idempotent daily-task step). Normal panel logins
are unaffected.
- Further hardening of the internal OAuth token endpoint: removed unused code that requested a token with a predictable
client secret through a grant that is not enabled, and added a per-client rate limit (fail-open) on the token
endpoint's client_credentials grant.
- Security Audit no longer flags the ModSecurity-provided Lua library as an "unowned file" on servers where ModSecurity
ships its own copy; the Ebury-style credential-stealer detection is unchanged (it still fires if a credential daemon
maps the library).
Secure Kernel:
- On EL8/EL9/EL10 the Secure Kernel is now installed together with the extra kernel modules that the firewall
(CSF/iptables) needs, and the panel refuses to install or switch to a kernel that is missing them. After switching to
the Secure Kernel the panel verifies that the firewall loaded and that outbound connectivity works, and automatically
rolls back to the previous kernel if either fails, so a server can never be left unreachable.
Web server:
- A domain set to a PHP-FPM version that is not installed (common after a restore, a migration, or after a PHP version
is removed) no longer breaks its site. The web server rebuild now switches the domain to a valid PHP-FPM version and
logs the correction, instead of generating a broken vhost that fell through to the wrong site/certificate on the same IP.
- PHP-FPM pools no longer write core dumps when an idle "ondemand" worker is recycled (rlimit_core is now 0), so the
disk and logs are no longer filled with core files on some PHP builds.
Backups:
- A backup that fails to write (for example the disk fills up mid-write) is no longer reported as successful. The
backup now checks the move's exit status, deletes the partial archive and marks the account as failed; it also checks
free space up-front and writes each archive to a temporary .part file renamed only after it completes, so a previous
good backup is kept and a restore can never pick up a half-written file.