Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,12 @@ exported. Retaining a candidate never selects it as the assessed version.

JSON, formula-neutralized CSV and a self-contained, script-free HTML report use the same validated evidence records. HTML supports escaped `--brand` and an optional bounded local raster `--logo`. See the [actual synthetic HTML example](docs/example-report.html); retained images in `docs/images/` are earlier concept artwork, not generated results.

Every report includes one UTC run assessment timestamp, the exact standalone
executable SHA-256, rule snapshot ID/date/hash and completeness. Empty and
interrupted CSV summaries retain the same provenance. Assessment time is distinct
from rule verification and evidence acquisition; build identity never attests a
deployed patch. Injected time/build metadata keeps synthetic library calls reproducible.

## Documentation and development

- [Reference](docs/REFERENCE.md): input schema, CLI, limits, outputs and exit policy
Expand Down
2 changes: 1 addition & 1 deletion SHA256SUMS
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
293da888b6c8cb667dc373f4a138dd94d9a76855a7420df5bca56a7aa252f593 sharp_rsvg_rce_check.py
da4132845194dce45f044b9446d177632996553281f9e22ba975fd51f42279bc sharp_rsvg_rce_check.py
dbcee01397d62d0017fea9319fcb8d59a36b5bf0dfe16556f890cca498c848f6 rules/snapshot.json
11 changes: 10 additions & 1 deletion docs/CONTRACT.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,16 @@ Unverified research leads must remain disabled or outside the active snapshot.
## Deterministic formats

Canonical JSON uses the same stable encoding as snapshot hashing. It includes
no runtime clock, absolute input path, or implicit filename-derived label.
no absolute input path or implicit filename-derived label. The run envelope includes
required `generated_at` (a real UTC `YYYY-MM-DDTHH:MM:SSZ` assessment timestamp) and
`tool.executable_sha256` (lowercase SHA-256 of the executing standalone bytes).
These identify this assessment run, not evidence acquisition or deployed patch state.
The CLI captures the envelope once and retains it through incomplete recovery.
`make_report` accepts injected values for deterministic fixtures; canonical assessment
results and rule hashing remain independent of the clock. CSV and HTML retain this
envelope together with rule snapshot ID, verification date, digest and completeness,
including empty reports. The new required fields update the closed schema-v1 report
contract; older report fixtures must add them rather than infer them from file dates.
Callers must traverse and order observations deterministically; list order is
preserved to avoid silently changing the meaning of configuration operations.

Expand Down
9 changes: 8 additions & 1 deletion docs/REFERENCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,14 @@ The checker does not collect credentials, hostnames, environment variables, proc

`--format json|csv|html` defaults to JSON on stdout. `--output FILE` publishes an atomic report in an existing directory. It refuses an existing destination unless `--force` is supplied. The scanner, inventory, supplied logo and their symlink/hard-link aliases remain protected with `--force`; output symlinks are rejected. No-clobber publication requires filesystem hard-link support and fails explicitly if unavailable. Reports are not incremental checkpoints; abrupt termination or output failure can prevent publication.

All formats share the [v1 evidence contract](CONTRACT.md). JSON includes the rule snapshot digest and `complete` flag, without a runtime timestamp. CSV serializes structured dimensions as JSON cells and prefixes strings that could become spreadsheet formulas. An interrupted report with no completed assets has a `record_type=summary` row. HTML escapes dynamic text, blocks remote resources, contains no scripts, supports printing, and accepts `--brand TEXT` and `--logo FILE` (PNG/JPEG/GIF/WebP, at most 1 MiB; logo only with HTML). No logo is selected by default.
All formats share the [v1 evidence contract](CONTRACT.md). JSON includes `generated_at` (UTC run assessment time), `tool.executable_sha256` (the executing standalone file's exact bytes), rule snapshot ID/date/hash and `complete`. The CLI captures time and digest once, reusing them if a handled interruption produces an incomplete report. This timestamp is not evidence acquisition time or rule verification time; a checker digest does not attest any deployed patch. Library callers can inject `generated_at` and `executable_sha256` into `make_report` for deterministic fixtures.

CSV retains all existing columns and appends `tool`, `tool_version`, `executable_sha256`, `generated_at`, `rules_snapshot_id`, and `rules_sha256` on result and empty summary rows. It serializes structured dimensions as JSON cells and neutralizes spreadsheet formulas, including summary metadata. An interrupted report with no completed assets has a `record_type=summary` row. HTML escapes dynamic text, displays run assessment time separately from rule verification, blocks remote resources, contains no scripts, supports printing, and accepts `--brand TEXT` and `--logo FILE` (PNG/JPEG/GIF/WebP, at most 1 MiB; logo only with HTML). No logo is selected by default. These provenance fields are required by the updated closed report schema; consumers of older schema-v1 report fixtures must update them together.

Invoking the standalone checker through an executable symlink hashes the resolved
checker file. Copied standalone files hash their own bytes. This exception applies
only to locating the executing checker; evidence and output symlink protections
remain unchanged.

Build numbers and asset IDs are operator-provided; review them before sharing a report. Invalid inventory/file errors use controlled descriptions instead of raw input paths or content. Argument-parser usage errors can include the explicit command-line arguments.

Expand Down
2 changes: 1 addition & 1 deletion docs/example-report.html
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
article,.callout{background:var(--surface);border:1px solid var(--line);border-radius:10px;padding:18px 22px;margin:20px 0}
pre{white-space:pre-wrap;overflow-wrap:anywhere;font-size:.85rem}p,li,code{overflow-wrap:anywhere}a{color:var(--accent)}summary{cursor:pointer}
footer{font-size:.85rem;color:var(--muted)}@media print{body{background:white;color:black}article{break-inside:avoid}details>summary{display:none}details>ul,details>pre{display:block}}
</style></head><body><main><header><div class='eyebrow'>CompleteTech LLC</div><h1>Security evidence report</h1><p>sharp-rsvg-rce-check 0.2.0 · rules verified 2026-10-24</p></header><div class='callout'><strong>Completed assessment</strong><p>Local exploitability is not tested. Version, configuration, candidate source patterns and external exploitation reports are separate evidence.</p><p>precondition_present: 1 · mitigated_configuration: 1 · fixed_version_reported: 1 · unknown: 1</p><ul><li>Offline supplied evidence and explicitly selected metadata only; library selection, deployed versions, provenance and effective mitigations are not independently attested.</li><li>No network requests, application execution, image decoding, exploitation, reachability test or compromise detection is performed.</li><li>The Sharp comparison covers exact stable 0.0-0.35 versions. Global librsvg has a documented remediation build, not a published independent affected-version range; only stable 2.63.2+ within 2.63 is accepted as reported remediation.</li><li>PIE is an RCE mitigation, not a library patch or a guarantee against other memory-corruption impact. Unknown libc or PIE remains unknown.</li></ul></div><article><h2>synthetic-bundle · Sharp (bundled librsvg)</h2><p class='status'>precondition_present</p><p>Reported version: <code>0.35.4</code> · Rule: <code>CVE-2026-96889</code> · Exploitability: <code>not_tested</code></p><p>For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.</p><ul><li>The reported official Sharp bundle is below 0.35.5.</li><li>Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.</li><li>A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.</li></ul><details><summary>Evidence and assessment dimensions</summary><ul><li>version: present — The reported official Sharp bundle is below 0.35.5.</li><li>inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.</li><li>inventory: present — Sharp version observation: 0.35.4. Accepted exact observations: 0.35.4.</li><li>inventory: unknown — librsvg version observation: missing, qualified or conflicting.</li><li>configuration: present — Reported platform: linux; reported libc: glibc. Other platforms do not establish that the underlying memory bug is absent.</li><li>configuration: present — Reported effective SVG decoder state: enabled. A blocked claim must cover VipsForeignLoadSvg in the deployed process.</li><li>configuration: present — Reported Node executable PIE state: disabled. This operator claim is not inferred from optional binary metadata hints.</li><li>configuration: present — Operator-reviewed untrusted SVG input path: present. No data-flow or reachability test is performed.</li></ul><pre>{
</style></head><body><main><header><div class='eyebrow'>CompleteTech LLC</div><h1>Security evidence report</h1><p>sharp-rsvg-rce-check 0.2.0 · Run assessed (UTC): 2026-10-25T12:34:56Z · Executable SHA-256: da4132845194dce45f044b9446d177632996553281f9e22ba975fd51f42279bc · rules verified 2026-10-24</p></header><div class='callout'><strong>Completed assessment</strong><p>Local exploitability is not tested. Version, configuration, candidate source patterns and external exploitation reports are separate evidence.</p><p>precondition_present: 1 · mitigated_configuration: 1 · fixed_version_reported: 1 · unknown: 1</p><ul><li>Offline supplied evidence and explicitly selected metadata only; library selection, deployed versions, provenance and effective mitigations are not independently attested.</li><li>No network requests, application execution, image decoding, exploitation, reachability test or compromise detection is performed.</li><li>The Sharp comparison covers exact stable 0.0-0.35 versions. Global librsvg has a documented remediation build, not a published independent affected-version range; only stable 2.63.2+ within 2.63 is accepted as reported remediation.</li><li>PIE is an RCE mitigation, not a library patch or a guarantee against other memory-corruption impact. Unknown libc or PIE remains unknown.</li></ul></div><article><h2>synthetic-bundle · Sharp (bundled librsvg)</h2><p class='status'>precondition_present</p><p>Reported version: <code>0.35.4</code> · Rule: <code>CVE-2026-96889</code> · Exploitability: <code>not_tested</code></p><p>For official bundled binaries, upgrade Sharp to 0.35.5 or a later supported patched release. For a global library, independently verify the selected librsvg and apply the upstream 2.63.2 fix or a documented vendor fix. Rebuild/redeploy and verify the actual linkage. Effective VipsForeignLoadSvg blocking and Node PIE are separate mitigations; neither attests the library patch set.</p><ul><li>The reported official Sharp bundle is below 0.35.5.</li><li>Version, platform, libc, effective mitigation and input-path observations are operator claims; local exploitability remains not_tested.</li><li>A mitigated configuration preserves an affected library/package assessment and does not establish safety or absence of prior compromise.</li></ul><details><summary>Evidence and assessment dimensions</summary><ul><li>version: present — The reported official Sharp bundle is below 0.35.5.</li><li>inventory: present — Operator-reported library selection: bundled; linkage is not independently verified.</li><li>inventory: present — Sharp version observation: 0.35.4. Accepted exact observations: 0.35.4.</li><li>inventory: unknown — librsvg version observation: missing, qualified or conflicting.</li><li>configuration: present — Reported platform: linux; reported libc: glibc. Other platforms do not establish that the underlying memory bug is absent.</li><li>configuration: present — Reported effective SVG decoder state: enabled. A blocked claim must cover VipsForeignLoadSvg in the deployed process.</li><li>configuration: present — Reported Node executable PIE state: disabled. This operator claim is not inferred from optional binary metadata hints.</li><li>configuration: present — Operator-reviewed untrusted SVG input path: present. No data-flow or reachability test is performed.</li></ul><pre>{
&quot;confidence&quot;: &quot;low&quot;,
&quot;mitigation&quot;: {
&quot;evidence_ids&quot;: [],
Expand Down
14 changes: 13 additions & 1 deletion schemas/report-v1.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,12 @@
"complete": {
"type": "boolean"
},
"generated_at": {
"format": "date-time",
"maxLength": 20,
"pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z(?![\\s\\S])",
"type": "string"
},
"limitations": {
"items": {
"maxLength": 2048,
Expand Down Expand Up @@ -459,6 +465,10 @@
"tool": {
"additionalProperties": false,
"properties": {
"executable_sha256": {
"pattern": "^[a-f0-9]{64}(?![\\s\\S])",
"type": "string"
},
"name": {
"maxLength": 128,
"pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]{0,127}(?![\\s\\S])",
Expand All @@ -473,14 +483,16 @@
},
"required": [
"name",
"version"
"version",
"executable_sha256"
],
"type": "object"
}
},
"required": [
"schema_version",
"tool",
"generated_at",
"rules",
"complete",
"limitations",
Expand Down
Loading
Loading