gDown Security

Security of gDown: how to report a vulnerability, which versions receive security fixes, how fixes and advisories reach you, and our duties under the EU Cyber Resilience Act.

Report a vulnerability

Write to <strong>beacon@gluonify.io</strong>, or use GitHub's private vulnerability reporting where the repository offers it. Please do not open a public issue. Give the version (gdown --version or the image tag), how to reproduce the problem and the impact you see.

We acknowledge within 3 working days and give you a tracking identifier, keep you informed, and credit you in the advisory if you wish. Default embargo: 90 days from the report, shorter once a fix is released. The contact is also in /.well-known/security.txt (RFC 9116).

Supported versions

  • Latest 0.x minor: security fixes, as patch versions.
  • Previous 0.x minor: security fixes for 3 months after the next minor is released.
  • Older versions: no fixes, upgrade.

From 1.0, the latest minor of each major version receives security fixes for <strong>5 years</strong> from the release of that major. The end date is stated in the release notes and on the installation page.

How fixes are delivered

  • Security fixes come in <strong>patch versions</strong> that change nothing else, free of charge.
  • They are signed: the Docker image gluonify/gdown with cosign, the executables installed by gdown.sh with the release key (signed manifest, SHA-256 of each file).
  • Each version ships a <strong>CycloneDX SBOM</strong>: a cosign attestation of type cyclonedx on the image, and manifest-sbom.json with one .cdx.json per executable on images.gluonify.io.

Check an image before you run it:

curl -fsSLO https://gdown.gluonify.io/cosign.pub
cosign verify --key cosign.pub gluonify/gdown:<version>
cosign verify-attestation --key cosign.pub --type cyclonedx gluonify/gdown:<version>

Advisories

An advisory is published with the fix, here and as a GitHub security advisory. It states:

  • the identifier, and the CVE when one is assigned;
  • the CVSS v4.0 score and vector;
  • the affected and the fixed versions;
  • a workaround, if there is one;
  • credit to the reporter, with their consent.

EU Cyber Resilience Act

gDown follows the vulnerability-handling process of the Cyber Resilience Act (Regulation (EU) 2024/2847). An actively exploited vulnerability or a severe incident is reported to the CSIRT designated as coordinator and to ENISA within 24 hours (early warning), 72 hours (notification) and then in a final report. Users are informed without undue delay, with the measures to take.

Do not publish details of an unfixed vulnerability before the advisory: nothing about it goes in a public issue, commit or branch.