Keygraph Shannon contains a hard-coded API key in its router configuration that, when the router component is enabled and exposed, allows network attackers to authenticate using the publicly known static key. An attacker able to reach the router port can proxy requests through the Shannon instance using the victim’s configured upstream provider API credentials, resulting in unauthorized API usage and potential disclosure of proxied request and response data. This vulnerability's general exploitability has been mitigated with the introduction of commit 023cc95.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
Low
Partial disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://github.com/KeygraphHQ/shannon/issues/186
disclosure@vulncheck.com
https://github.com/KeygraphHQ/shannon/pull/224
disclosure@vulncheck.com
https://github.com/KeygraphHQ/shannon/pull/224/changes/023cc953db742602964b7826…
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/keygraph-shannon-hard-coded-router-api-key
disclosure@vulncheck.com