circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#513 Security hardening: the Docker image’s runtime user can write the application code

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#513
  • issue
  • state:closed

**Docker app image: the runtime user can write the application code.** - Location: deploy/Dockerfile.app:243-248 (`COPY --chown=node:node` for `.next/standalone`, `server`, `dist`), with `USER node` at line 257. - Impact: after RCE, the attacker can modify code to persist across requests (not across a container re-create). - Fix: copy as root:root, read-only, and leave only a cache dir writable. Consider `read_only: true` with a tmpfs in compose.yml. --- From the security review of 2026-11-06 (commit 6776c44), finding I-12: hardening or information, filed publicly because it describes no way in. The exploitable findings are private security advisories. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/issues/513

Related

Open #513 Security hardening: the Docker image’s runtime user can write the application code in the timeline

#513 Security hardening: the Docker image’s runtime user…