Menu

The Alert Said 'Not Applied in Production' — a Nightly Timer Had Already Done It, One Hour Earlier
📰

The Alert Said 'Not Applied in Production' — a Nightly Timer Had Already Done It, One Hour Earlier

DEV Community: security·sunah kim·about 9 hours ago
#ERPTY7Aw
#devtosecurity#devto#dev#production#applied
Long article (769 words) — no AI summary yet.
Reading 0:00
15s threshold

Intro

One morning my security-research routine fired an urgent alert: "PHP 8.3.37 (released 11/19) contains an important fix. Production is on 8.3.36 — not applied . Patch ASAP."

I rushed into the server. Production was already on 8.3.37 , php-fpm restarted and all. The previous night's auto-update timer had finished the job. The box that was actually behind was dev. We even have a gate — "dev goes first, production only runs if dev succeeded" — so how did production overtake dev? The cause was a one-hour gap between the repository publishing the package and the two timers firing .

The setup

Dev and production run the same Linux distribution, and a systemd timer applies security updates every night:

23:00 — dev's timer runs dnf upgrade and records the result in a state file

00:00 — production's timer runs dnf upgrade only if dev's state file says "success", and restarts php-fpm if PHP was updated

Separately, a web-only research routine reads vulnerability feeds every morning and reports.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.