Fix cross-origin policy accepts any origin in Hapi

The CORS configuration accepts requests from any origin. Combined with credentials this lets any site a logged-in user visits make authenticated calls to the API and read the responses. Without credentials it may be intentional for a public API - the finding says which case it found.

medium likely Hapi CWE-942 / OWASP A05:2021

The vulnerable pattern in Hapi

MEDIUM likely Cross-origin policy accepts any origin A05:2021 src/server.ts:41:5 39 │ // (Route-level cors plugin shapes vary; header calls are detected reliably.) 40 │ const response = h.response({ ok: true }) 41 │ response.header('Access-Control-Allow-Origin', '*') │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ accepts requests from any origin 42 │ response.header('Access-Control-Allow-Credentials', 'true') 43 │ return response

This finding comes from the Hapi fixture in the owlwarden test suite. Any origin may call this API and read the response. That is a deliberate choice for a public endpoint and a mistake for anything behind a session - nothing in the source says which this is, so it is reported for you to decide.

The corrected handler

Give the route's cors option an explicit origin list.

server.route({
  method: 'GET',
  path: '/api/data',
  options: {
    cors: {
      origin: ['https://app.example.com'],
      credentials: true,
    },
  },
  handler: (request, h) => h.response({ ok: true }),
})

If you are not using Hapi

Replace the wildcard with the origins that actually need access, and only send credentials to those.

Check your own repository

npx owlwarden scan
npx owlwarden explain cors-permissive

Runs on your machine. No account, no telemetry, no network unless you ask. In CI, SARIF uploads to code scanning and the exit code is the gate.

Other Hapi checks

Rules with a tested Hapi example.

cors-permissive for every framework / All rules / owlwarden