Files
ZitPlane/project/DEPENDENCY-SECURITY.md
T

42 lines
5.7 KiB
Markdown

# ZitPlane P05-SEC-01 — Dependency Provenance, Vulnerabilities and Exact Patch Records
**Baseline:** `1a602551ad9a791efcc594834f2fa6ce748339ae`
**Reference:** Gitea Run #83 security job #173, 2026-11-22. The source-only regenerated npm/pnpm lockfiles are **not CI acceptance** until the subsequent focused security workflow verifies frozen installs and registry advisory results.
## Advisory inventory (19 prior reported records)
`npm audit` reported **one affected Account Next.js package** associated with **seven IDs**, not seven different installed npm packages. `pnpm audit --prod` reported **18 Login Moderate records**, representing 7 Next.js IDs, 8 OpenTelemetry driver instrumentation records under a *single GHSA*, 1 HTTP instrumentation advisory, 1 glob and 1 minimatch. Previous HIGH/CRITICAL counts were zero.
| ID / Group | Affected package(s) and old pin | Verified immediate dependency parent | Security impact / required patched range | Source resolution, pending CI |
| --- | --- | --- | --- | --- |
| Seven Next.js GHSAs below | Account + Login direct `next@16.4.3` | Each application `package.json` | Information/cross-user cache disclosure/poisoning, SVG bypass, Edge HttpOnly header exposure and cross-client response injection; npm fix `16.4.6` | Both apps pin `next@16.4.6` in approved manifest/lock |
| `GHSA-qqmp-wf37-98f9` (8 records) | `@opentelemetry/instrumentation-{pg,mysql2,knex,mysql,mongoose,oracledb,tedious,cassandra-driver}` | `@opentelemetry/auto-instrumentations-node@0.76.0` direct production Login dependency | Database account username exposed as `db.user` in spans. Fixed: pg >=0.73.0; mysql2/mysql/mongoose >=0.67.0; knex >=0.65.0; oracledb >=0.46.0; tedious >=0.40.0; cassandra >=0.66.0 | Coordinated parent `auto-instrumentations-node@0.80.0` + `sdk-node@0.222.0` selects patched minors |
| `GHSA-3v2p-hm54-8qcq` | `@opentelemetry/instrumentation-http@0.218.0` | `@opentelemetry/auto-instrumentations-node@0.76.0` | Moderate HTTP instrumentation issue, patched >=0.222.0 | `auto-instrumentations-node@0.80.0` requires `instrumentation-http@^0.222.0` |
| `GHSA-3g3m-2fjr-6pw4` | `glob@10.5.0`; old lock also `13.0.6` | Snapshot immediate parents: `@npmcli/map-workspaces@3`, `@npmcli/package-json@5`, `rimraf@5`, `archiver-utils@5`, `unified-engine@11`; old `cacache@20` also referenced glob13 | Aborted glob traversal may continue performing costly filesystem operations, risking availability; patched >=14.0.2 | **OPEN**: major 14 not permitted by parent semver/approved root overrides; current workspace YAML read-only |
| `GHSA-g3hv-75wg-m249` | `minimatch@10.2.5/10.2.6`; old lock also v9 | Snapshot immediate parents include `eslint@10.8.1`, `@eslint/config-array@0.23.5`, `@typescript-eslint/typescript-estree@8.67.0`, `nx@22.7.12`, `@netlify/build-info@10.5.1` and `glob@13.0.6` | Potential globparts amplification denial of service, patched >=11.0.1 | **OPEN**: major 11 needs compatible transitive parent update or audited PNPM workspace override, outside exact write scope |
### Seven GitHub advisory IDs affecting Next.js 16.4.3
`GHSA-mfr8-8qww-v76h`, `GHSA-vc7v-qv4w-wrv8`, `GHSA-7qx7-33qx-rqx2`, `GHSA-f3mh-rxg3-f5g2`, `GHSA-pc58-hwjq-p385`, `GHSA-rhh4-g77r-r9qj`, `GHSA-vvgp-ww4w-46vf`.
Original audit: Login Next fixed >=16.4.5; Account npm recommends >=16.4.6, so **16.4.6 exact** chosen for both plus matching `@next/eslint-plugin-next` (Login dev only). See https://www.npmjs.com/package/next and original Gitea security logs.
### Transitive parent and compatibility detail
This table identifies **immediate parents present in the archived PNPM lock graph**, not a claim that every vulnerable package is loaded at runtime or exploitable over a public request. Actual production reachability remains UNVERIFIED without a separate controlled analysis. PNPM's `--prod` audit flagged these lockfile packages, so they must not be suppressed solely because many parents are dev tools.
`auth/ui/v2/pnpm-workspace.yaml` already owns other root overrides and is explicitly READ ONLY in this phase. A `pnpm.overrides` entry in root `package.json` would conflict with or be ignored in the presence of workspace-defined overrides on modern PNPM; **no ineffective fake override is added**. Minimatch 11/glob 14 are semver major changes; forcing them without compatibility proof is disallowed.
### Reproducible lockfile / provenance rules
- Account npm v3 lock was generated by `npm install --package-lock-only --ignore-scripts --no-audit --no-fund`; **no app install/build/test**.
- Login pinned `pnpm@10.30.3` lock was generated by `pnpm install --lockfile-only --ignore-scripts --no-frozen-lockfile`; no project `node_modules`. The four imported PNPM workspace members and prior root overrides are unchanged.
- PNPM's lockfile-only regeneration removed prior unreachable snapshots inherited from a much larger official ZITADEL monorepo. Source files/proto/Login UI/auth code are unchanged. Compare exact Git diff: this is **lock resolution metadata**, not removal of application features.
- Security acceptance is only the single Gitea workflow run: frozen npm/pnpm installs, locked build/regression and live npm/pnpm advisory results. No blind blanket update, no lockfile hand-edited integrities.
## Source-level candidate and acceptance
Expected patched direct candidates: Next.js `16.4.6` both apps; Login `@opentelemetry/auto-instrumentations-node@0.80.0`, `@opentelemetry/sdk-node@0.222.0`, `@opentelemetry/api-logs@0.222.0`. **OPEN candidate blockers:** glob >=14.0.2, minimatch >=11.0.1 require separately approved scoped parent/override changes.
**CI PENDING:** live audit may expose new or unchanged vulnerabilities; never declare zero Moderate from manifest text alone. The follow-up result record will list all remaining exact IDs, job statuses and a separate narrow remediation plan.