docs: record P05 security run 87 and two moderate blockers
This commit is contained in:
1 parent
752d243ae8
commit
43eee54e7a
18 files changed
+77
-16
No files matched your search
+1
-1
@@ -12,6 +12,6 @@ This is the chronological **index**. Phase-specific scope/implementation evidenc
|
||||
| 2026-11-22 | P05-CI-01 | Gitea verification workflow, dependency lock reconciliation, narrow checkout remediation | Run #81: 2 PASS/2 FAIL; 1219 Login tests PASS, Account TS2345 and Docker checkout blocked; see [P05-CI-01.md](P05-CI-01.md) |
|
||||
| 2026-11-22 | P05-CI-02 | Narrow Auth.js TS2345 fix, CI negative tests, advisory triage and post-run portless override | Run #83: Account/Login/Security PASS, Docker FAIL on host 8080; cleanup PASS; portless override unverified. [Evidence](P05-CI-02.md) |
|
||||
| 2026-11-22 | P05-CI-03 | Backend-only Gitea verification of portless Compose, 4 services, Postgres persistence, OIDC/JWKS and safe cleanup | **Run #86 SUCCESS** on `03fb589`, no unrelated suites rerun; [evidence](P05-CI-03.md) |
|
||||
| 2026-11-22 | P05-SEC-01 | Narrow Next.js 16.4.6 and compatible OTel instrumentation security versions, frozen lockfiles, strict CI advisory gate | Implementation source staged; one Gitea security acceptance run pending; [details](P05-SEC-01.md) |
|
||||
| 2026-11-22 | P05-SEC-01 | Next.js 16.4.6, compatible OTel instrumentation, frozen locks and strict advisory gates | Run #87: 3 PASS/1 FAIL; 17/19 prior findings no longer reported, 2 Moderate Login blockers. [Evidence](P05-SEC-01.md) |
|
||||
|
||||
Rules: Append new phases or fixes; never silently rewrite a past result. Separate **implemented**, **verified**, **blocked**, and **proposed**. Never log a user secret or personal data.
|
||||
+1
-1
@@ -8,7 +8,7 @@
|
||||
| [P05-CI-01.md](P05-CI-01.md) | Scope/roots, allowed paths, implementation and Gitea CI acceptance evidence | P05-CI-01 / source complete, CI blockers open |
|
||||
| [P05-CI-02.md](P05-CI-02.md) | Auth.js narrow patch, isolated Gitea CI gate, advisory triage and exact acceptance evidence | P05-CI-02 / run #83 completed; residual Docker gate blocked |
|
||||
| [P05-CI-03.md](P05-CI-03.md) | Backend-only pre-change scope, disposable CI run evidence and exact acceptance result | P05-CI-03 / Run #86 SUCCESS; acceptance complete |
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Pre-change security scope, remediation, exact advisory evidence, one CI run and closure | P05-SEC-01 / source prepared, CI pending |
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Pre-change security scope, remediation, exact advisory evidence, one CI run and closure | P05-SEC-01 / Run #87 completed, 2 Moderate open |
|
||||
| [CHANGELOG.md](CHANGELOG.md) | Short append-only chronological phase log and links to detailed reports | DOCS-01 / active |
|
||||
|
||||
Update this manifest whenever any direct child file or directory changes. Use **actual source state**; a planned file must be labeled planned, not present.
|
||||
+32
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
**Date:** 2026-11-22
|
||||
**Approved baseline:** `1a602551ad9a791efcc594834f2fa6ce748339ae` (Gitea `main`)
|
||||
**Pre-change status:** APPROVED / PLAN LOCKED; source edits not started.
|
||||
**Final status:** PATCH IMPLEMENTED; one focused Gitea Run #87 completed **3 PASS / 1 FAIL**. Security acceptance **BLOCKED** by 2 Moderate Login transitive advisories; documentation-only closure.
|
||||
**Prior evidence:** Gitea Run [#83](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/83) security job #173; Run [#86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86) disposable backend ACCEPTED.
|
||||
|
||||
## Exact Scope Lock
|
||||
@@ -45,3 +45,34 @@ Root source pins `next@16.4.3`; npm registry advisory shows vulnerable 16.0.0–
|
||||
## Phase evidence ledger
|
||||
|
||||
**PENDING.** Update with actual modifications and one focused CI run SHA/job conclusions. If Moderate remain, security closure must stay **BLOCKED**, not silently accepted.
|
||||
|
||||
|
||||
## Actual implementation, CI evidence and acceptance — 2026-11-22
|
||||
|
||||
**Source commit:** `752d243ae8fb24ce3cfa990343082e2d0431306b` pushed to Gitea `main` before dispatch.
|
||||
**ONE focused run:** [#87](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/87), `workflow_dispatch`, `main`, tested exact SHA above. Started 2026-11-22 14:08:50 UTC, completed 14:12:42 UTC. **OVERALL FAILURE** by design due remaining Moderate Login advisories; **3 PASS / 1 FAIL**, no second run.
|
||||
|
||||
| Job | Gitea job ID | Final | Real log markers/evidence |
|
||||
| --- | ---: | --- | --- |
|
||||
| Account frozen build | 185 | **PASS** | `ZITPLANE_SECURITY_SOURCE_LOCK_CONTRACT_PASS`, npm ci, `tsc --noEmit`, Next `16.4.6` production build, `ZITPLANE_SECURITY_ACCOUNT_BUILD_PASS`; anonymous API HTTP 401/no-store and protected redirect `ZITPLANE_SECURITY_ACCOUNT_NEGATIVE_REGRESSIONS_PASS` |
|
||||
| Official Login V2 frozen build/unit | 186 | **PASS** | `pnpm@10.30.3 install --frozen-lockfile` resolved **1131** packages, `ZITPLANE_SECURITY_LOGIN_FROZEN_INSTALL_PASS`; Nx proto/client/Next `16.4.6` standalone build `ZITPLANE_SECURITY_LOGIN_BUILD_PASS`; **84/84 files, 1219/1219 tests PASS**, `ZITPLANE_SECURITY_LOGIN_UNIT_PASS` |
|
||||
| Account production security | 187 | **PASS** | npm `--omit=dev`, `0 vulnerabilities`; `ZITPLANE_NPM_ZERO_MODERATE_HIGH_CRITICAL_PASS`; Moderate=0, High=0, Critical=0 |
|
||||
| Login production security | 188 | **FAIL (strict gate)** | `pnpm audit --prod --audit-level high` PASS High/Critical threshold; registry reports **2 Moderate**, 0 High/Critical. `ZITPLANE_PNPM_SECURITY_ACCEPTANCE_BLOCKED=2` correctly terminates the job |
|
||||
|
||||
### Exact remaining findings — verified on Run #87
|
||||
|
||||
1. **`GHSA-3g3m-2fjr-6pw4` — `glob`**, Moderate. Current lock includes `glob@10.5.0`; advisory range >=9.0.0 <=14.0.1; patched **>=14.0.2**. Prior lock immediate parents: `@npmcli/map-workspaces@3.0.6`, `@npmcli/package-json@5.2.1`, `rimraf@5.0.10`, `archiver-utils@5.0.2`, `unified-engine@11.2.2`. Transitive major-version compatibility not proved.
|
||||
2. **`GHSA-g3hv-75wg-m249` — `minimatch`**, Moderate. Current lock includes `minimatch@10.2.5/10.2.6`; advisory range >=7.0.0 <11.0.1; patched **>=11.0.1**. Immediate parents include `eslint@10.8.1`, `@eslint/config-array@0.23.5`, `@typescript-eslint/typescript-estree@8.67.0`, `nx@22.7.12`. Forcing major 11 needs scoped parent/PNPM override compatibility verification.
|
||||
|
||||
The original 18 Moderate Login advisory records are now **2** (16 disappeared from registry audit: Next.js seven + OpenTelemetry 9); original Account one affected `next` package is now zero. **17 of the 19 previously reported records no longer reproduce**; do not imply these 17 correspond to 17 distinct CVEs. No High/Critical reported on either audit. **Security FULL ACCEPTANCE BLOCKED** until remaining two are remediated and CI-reverified.
|
||||
|
||||
### Scope/patch provenance and safety
|
||||
|
||||
- Only approved `users/ui/{package.json,package-lock.json}`, `auth/ui/v2/apps/login/package.json` and `auth/ui/v2/pnpm-lock.yaml` changed among application/workspace files.
|
||||
- Next exact `16.4.6` (both apps) and Login `@next/eslint-plugin-next` `16.4.6`; Login `@opentelemetry/auto-instrumentations-node@^0.80.0`, `@opentelemetry/sdk-node@^0.222.0`, `@opentelemetry/api-logs@^0.222.0`. Original Login V2 **auth/UI source**, Account `src/**`, developer Compose, Go backend, `pnpm-workspace.yaml` and production unchanged.
|
||||
- npm/pnpm lock files were regenerated metadata-only, without project `node_modules` or local build/test. Full imported upstream lock pruning removed 912 unused prior package key entries and introduced 88 new resolution entries; CI `--frozen-lockfile` **PASS** and all 1,219 unit regressions PASS.
|
||||
- Source-level audit: 29 approved staged files, 0 unauthorized, 0 secrets; 729 Git-tracked paths inventoried; all five relevant MINIFEST direct-child inventories exact. `AI_INSTRUCTIONS.md` untracked and untouched.
|
||||
- **No second Gitea run**, no local application builds/tests/dev server, no real users, no production deployment, no dependency versions beyond documented scope.
|
||||
- `auth/ui/v2/pnpm-workspace.yaml` is **read-only in this phase** and already owns PNPM root overrides. Do not place ineffective overrides in root `package.json` or force semver majors as an undocumented workaround. Future **P05-SEC-02** must explicitly approve narrow PNPM workspace override/parent changes and CI proofs, with a new baseline.
|
||||
|
||||
**Final verdict:** Minimal security remediation source patch and regression verification **DONE**, full Moderate+ security acceptance **BLOCKED** by exactly two named packages. The final documentation-only SHA is *not* the tested source SHA `752d243`.
|
||||
Reference in new issue
Block a user