Skip to content

fix(deps): bump hono, tar, dompurify, sharp to patch known CVEs - #3807

Open
aeonframework wants to merge 1 commit into
heygen-com:mainfrom
aeonframework:security/bump-hono-tar-dompurify-sharp
Open

fix(deps): bump hono, tar, dompurify, sharp to patch known CVEs#3807
aeonframework wants to merge 1 commit into
heygen-com:mainfrom
aeonframework:security/bump-hono-tar-dompurify-sharp

Conversation

@aeonframework

Copy link
Copy Markdown

Automated dependency bump to address several disclosed CVEs found via osv-scanner.

Packages bumped

Package From To Advisories closed Highest severity
hono ^4.0.0/^4.6.0 (cli, engine, gcp-cloud-run, producer, studio-server) ^4.13.5 19 (GHSA list below) HIGH — GHSA-88fw-hqm2-52qc (CORS middleware reflects any Origin with credentials)
tar ^7.4.3 (aws-lambda, gcp-cloud-run) ^7.5.21 6 CRITICAL — GHSA-23hp-3jrh-7fpw
dompurify ^3.2.4 (studio) ^3.4.13 3 MODERATE — sanitizer-bypass class
sharp ^0.35.0 (cli) ^0.35.4 1 HIGH — GHSA-rgj7-g3m4-5g8c

All four target versions are OSV-verified clean (api.osv.dev query against the bumped version returns zero vulnerabilities) and stay within the current major, so this should be a drop-in bump.

Reachability notes

  • hono: none of this repo's own code imports the specific vulnerable surfaces (hono/cors, hono/jwt, serve-static, the AWS Lambda / Lambda@Edge adapters) — grepped the whole packages/*/src tree and found no usage. hono is still the HTTP framework underpinning every network-facing surface here (the Studio/CLI preview server, the Cloud Run distributed-render handler), so this is defense-in-depth rather than a confirmed-reachable fix.
  • tar: used by aws-lambda/gcp-cloud-run to pack/unpack distributed-render artifacts — a real, shipped runtime path.
  • dompurify: this is the project's XSS sanitizer (packages/studio/src/components/storyboard/StoryboardSourceEditor.tsx's markdown preview). Checked the one call site against the three advisories' preconditions — it calls DOMPurify.sanitize(html) with no IN_PLACE option and no setConfig()/uponSanitizeAttribute hook, so it isn't hit by any of the three bypass classes today. Bumping anyway since it's the sanitizer of record.
  • sharp: used in the CLI's image-processing/capture pipeline.

Not bumped

adm-zip@0.6.0 also has an open advisory (GHSA-vwc7-r8mq-g2x9, extraction follows destination symlinks) but no fixed version exists yet upstream — nothing to bump to, flagging for awareness only.

Caveat

Manifest-only (package.json) — bun/bun install wasn't available in this run's sandbox to regenerate bun.lock. Please run bun install (root) to refresh the lockfile; the caret ranges above already resolve to a clean version once regenerated.

Detected by osv-scanner, cross-checked against api.osv.dev. No code changes outside dependency manifests.


Filed by Aeon.

hono 4.0.0/4.6.0 -> 4.13.5: closes 19 GHSA advisories (highest: GHSA-88fw-hqm2-52qc,
CORS middleware credential-reflection, HIGH) across cli/engine/gcp-cloud-run/
producer/studio-server. None of the vulnerable middleware (cors/jwt/serve-static/
lambda adapters) is imported by this repo's own code, but hono is the HTTP
framework underpinning every network-facing surface (Studio/CLI preview server,
Cloud Run distributed-render handler), so keeping it current is defense-in-depth.

tar 7.4.3 -> 7.5.21 (aws-lambda, gcp-cloud-run): closes 6 advisories including
GHSA-23hp-3jrh-7fpw (CRITICAL). Used to pack/unpack distributed-render artifacts.

dompurify 3.2.4 -> 3.4.13 (studio): closes 3 advisories (moderate sanitizer-bypass
class). The one call site (StoryboardSourceEditor markdown preview) doesn't use
the vulnerable IN_PLACE/setConfig()+uponSanitizeAttribute patterns, so not
independently confirmed reachable here, but this is the project's XSS sanitizer.

sharp 0.35.0 -> 0.35.4 (cli): closes GHSA-rgj7-g3m4-5g8c (HIGH).

All four targets OSV-verified clean at the bumped version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant