Skip to content

All versions since 1.9.1

1.9.1

Upgrading

After upgrading an existing installation, run cxg pentest install --force. The fix below is in the embedded Python pentest pipeline, and replacing the binary alone does not replace the files under ~/.cert-x-gen/pentest/.

Fixed

  • cxg.oracle.excludedRecords verdicts bind when the scope has a path. With a landing scope such as --scope http://host/dashboard, the oracle measured /api/x at the service origin while the finding claimed /dashboard/api/x, so a correct row-filtering fix came back inconclusive_refusal (unverified) instead of refuted (proven), and a leak was not confirmed by the oracle. The claim is now resolved at the service origin, the way the oracle’s requests are, through both cxg scan and cxg pentest run. The other class oracles build their requests from the full --target, so their claims already bound and are unchanged.
  • cxg pentest run --help described 1.8.0 session behaviour. It said a dead session only warns without --ci and that --skip-health-check force-marks profiles alive. Since 1.9.0 an expired profile exits 5 with or without either flag, and probes for ready services still run. The --ci, --skip-health-check and exit-code 5 help now say so, and --ci reads as what it still does: refuse a world-accessible --auth-dir.

[1.9.2] Latest

Upgrading

After upgrading an existing installation, run cxg pentest install --force. These fixes are in the embedded Python pentest pipeline. cxg scan refreshes it on first use.

Fixed

  • A profile is no longer unverified, and the run no longer exits 5, because the app has no JSON /api/me. When no liveness endpoint is configured and /api/me answers 404, HTML, a redirect or nothing, the 1.8.0 landing test decides; a configured endpoint, or an /api/me answering 401/403, still decides as in 1.9.x. Remaining 1.8.0 hole: an app with no API liveness endpoint, a public landing page and an expired bearer reads as alive.
  • A supplied-probe replay drops --auth names with no loadable profile, as 1.8.0 did, so one missing profile no longer makes every kit, including anonymous ones, exit 5.
  • Identity traffic and liveness go to the --scope target again. A profile’s saved --target origin is used only for a profile imported with --service; 1.9.x sent a stale profile’s requests to another port while the verdict was recorded against the scope.
  • Request helpers keep the --scope path prefix again, so cxg.fetch/raw/url and cxg.page.probeXss agree under a scope such as http://host/app/ and an XSS that 1.8.0 confirmed confirms. cxg.oracle.excludedRecords still resolves at the origin.
  • A complete run reports status: "ok", not "complete", so a consumer that treats any status other than ok as a caveat no longer reports one; incomplete is unchanged.
  • A blocked or failed request no longer changes the exit code to 4. It is still recorded in request_failures and makes the run status: incomplete.