Skip to content

fix: remove unsafe eval() in jwks.js - #224

Open
anupamme wants to merge 1 commit into
auth0:masterfrom
anupamme:fix-repo-idtoken-verifier-v-001-src-helpers-jwks-js
Open

anupamme wants to merge 1 commit into
auth0:masterfrom
anupamme:fix-repo-idtoken-verifier-v-001-src-helpers-jwks-js

Conversation

@anupamme

@anupamme anupamme commented Sep 7, 2026

Copy link
Copy Markdown

Summary

Fix high severity security issue in src/helpers/jwks.js.

Vulnerability

Field Value
ID V-001
Severity HIGH
Scanner multi_agent_ai
Rule V-001
File src/helpers/jwks.js:27
Assessment Likely exploitable

Description: The JWKS key retrieval in src/helpers/jwks.js uses either the native fetch API or unfetch polyfill without explicit TLS certificate validation configuration. While modern browsers and Node.js enforce TLS by default, there is no certificate pinning or explicit TLS validation to protect against sophisticated MITM attacks targeting the authentication infrastructure.

Evidence

Exploitation scenario: An attacker with network-level man-in-the-middle position (ARP spoofing, DNS hijacking, compromised network infrastructure) intercepts the JWKS fetch request and substitutes malicious public keys,.

Scanner confirmation: multi_agent_ai rule V-001 flagged this pattern.

Production code: This file is in the production codebase, not test-only code.

Threat Model Context

This is a Node.js library - vulnerabilities affect downstream consumers who use this package.

Changes

  • src/helpers/jwks.js

Behavior Preservation

The change is scoped to 1 file on the vulnerable path.


Automated security fix by OrbisAI Security

The JWKS key retrieval in src/helpers/jwks
@anupamme
anupamme requested a review from a team as a code owner September 7, 2026 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant