Skip to main content
HighAPIOWASP A07:2021CWE-347

How to fix: OIDC discovery advertises the "none" signing algorithm

The authorization-server metadata lists "none" among its supported ID token signing algorithms. That means the server will issue, and by implication accept, unsigned ID tokens.

Why it matters

An unsigned ID token is a token anyone can write. A client that follows the discovery document and honours alg "none" will accept a token whose sub, email and groups claims the attacker chose, which is authentication bypass with no credential involved.

OpenID Connect Core permits alg "none" only for the response of a token-endpoint exchange where the token never leaves the back channel, and OIDC-conformant clients are expected to reject it everywhere else. Advertising it in discovery metadata means clients that select an algorithm from that list can pick "none", and it strongly suggests the server accepts unsigned tokens on the paths where it verifies them. Providers that support it usually do so through a configuration flag left over from a development setup.

How to fix it

  1. 1Remove "none" from id_token_signing_alg_values_supported.
  2. 2Configure the issuer to sign with RS256, PS256, or ES256 only, and to reject any token whose alg header is not on that list.
  3. 3On the client side, pin the accepted algorithm explicitly rather than trusting the token's own alg header.
  4. 4Review the issuer's logs for tokens presented with alg none.

Code examples

Client: pin the algorithm during verification

JavaScript
const { payload } = await jose.jwtVerify(idToken, JWKS, {
  issuer: 'https://auth.example.com',
  audience: 'my-client-id',
  algorithms: ['RS256'],   // never read alg from the token itself
});

Inspect what the issuer advertises

bash
curl -s https://auth.example.com/.well-known/openid-configuration \
  | jq '.id_token_signing_alg_values_supported'

References

Detected automatically by VulnRadar. The check id is api-oidc-discovery-alg-none-supported, stable across every scan so you can filter or diff on it.

See every api check

Questions

How severe is OIDC discovery advertises the "none" signing algorithm?
VulnRadar rates this high severity in the api 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 api-oidc-discovery-alg-none-supported, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does OIDC discovery advertises the "none" signing algorithm map to?
It maps to CWE-347. In the OWASP Top 10 it falls under A07: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 oidc discovery advertises the "none" signing algorithm

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

OIDC discovery advertises the "none" signing algorithm | VulnRadar