High
Implicit flow advertised
MCPS-AUTH-009Why it mattersThe implicit flow puts the access token in the browser's address. RFC 9700 advises against it, and OAuth 2.1 drops it.
How to fixRemove token from response_types_supported and use the code flow with PKCE.
- Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me- What we saw
response_types_supported: ["code","none","id_token","token","id_token token","code id_token","code token","code id_token token"]
Seen in the server's answer
SpecRFC 9700, Section 2.1.2 (Implicit Grant)
High
Password grant advertised
MCPS-AUTH-010Why it mattersThe password grant hands the person's password to the client. RFC 9700 says it must not be used.
How to fixRemove password from grant_types_supported.
- Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me- What we saw
grant_types_supported: ["authorization_code","client_credentials","implicit","password","refresh_token","urn:ietf:params:oauth:grant-type:device_code","urn:ietf:params:oauth:grant-type:jwt-bearer","urn:ietf:params:oauth:grant-type:token-exchange","urn:ietf:params:oauth:grant-type:uma-ticket","urn:o…
Seen in the server's answer
SpecRFC 9700, Section 2.4 (Resource Owner Password Credentials Grant MUST NOT be used)
Low
No Strict-Transport-Security header
MCPS-HDR-001Why it mattersWithout it, an attacker can keep a browser on plain HTTP on any later visit. HSTS makes the browser use HTTPS only.
How to fixSend Strict-Transport-Security: max-age=31536000 on every HTTPS response.
return new Response(body, { headers: { 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' } })app.use((req, res, next) => { res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains'); next() })- Request
POST https://api.assign2me.com/mcp (initialize)- Answer
401- What we saw
no Strict-Transport-Security
Seen in the server's answer
SpecRFC 6797 (HTTP Strict Transport Security)
Low
No X-Content-Type-Options: nosniff
MCPS-HDR-002Why it mattersA browser may guess a response's type and render JSON or text as HTML or script.
How to fixSend X-Content-Type-Options: nosniff on every response.
res.setHeader('X-Content-Type-Options', 'nosniff')- Request
POST https://api.assign2me.com/mcp (initialize)- Answer
401- What we saw
no X-Content-Type-Options: nosniff
Seen in the server's answer
SpecFetch Standard, X-Content-Type-Options
Low
PKCE plain method offered
MCPS-AUTH-008Why it mattersWith plain, the challenge equals the secret, so anyone who sees the request sees the secret.
How to fixOffer S256 only.
- Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me- What we saw
code_challenge_methods_supported: ["plain","S256"]
Seen in the server's answer
SpecRFC 9700, Section 2.1.1 (PKCE: S256)