Skip to main content
LowHeadersOWASP A02:2021CWE-319

How to fix: Reporting-Endpoints Defines a Plaintext HTTP Endpoint

The Reporting-Endpoints header defines one or more report delivery URLs using http:// instead of https://.

Why it matters

Reports sent to an http:// endpoint, covering CSP violations, COOP/COEP violations, deprecations, and crash reports, travel in plaintext and can be read or altered by anyone on the network path. Many browsers also refuse to deliver reports from an HTTPS page to a plain HTTP collector at all, so the reports may simply be dropped.

Reporting-Endpoints maps a group name to the URL the browser POSTs reports to. Report bodies can include the violating page's URL, referrer, user agent, and details about the resource that triggered the report. That collector endpoint should always be https://, both to protect that data in transit and because secure-context report delivery to an insecure endpoint is unreliable by design.

How to fix it

  1. 1Serve the reporting collector over HTTPS.
  2. 2Update the Reporting-Endpoints header to reference the https:// URL for every group name.

Code examples

Reporting-Endpoints over HTTPS

text
Reporting-Endpoints: default="https://reports.example.com/collect"

References

Detected automatically by VulnRadar. The check id is reporting-endpoints-insecure-url, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Reporting-Endpoints Defines a Plaintext HTTP Endpoint?
VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id reporting-endpoints-insecure-url, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Reporting-Endpoints Defines a Plaintext HTTP Endpoint map to?
It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for reporting-endpoints defines a plaintext http endpoint

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Reporting-Endpoints Defines a Plaintext HTTP Endpoint | VulnRadar