> For the complete documentation index, see [llms.txt](https://reports.immunefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reports.immunefi.com/shardeum-ancillaries-ii/35157-w-and-a-insight-unauthorized-access-to-shardeum-config-store-using-default-credentials.md). # #35157 \[W\&A-Insight] Unauthorized Access to Shardeum Config Store using default credentials **Submitted on Sep 7th 2024 at 16:30:22 UTC by @sujan\_shetty for** [**Audit Comp | Shardeum: Ancillaries II**](https://immunefi.com/audit-competition/shardeum-ancillaries-ii-boost) * **Report ID:** #35157 * **Report Type:** Websites and Applications * **Report severity:** Insight * **Target:** * **Impacts:** * Unauthorized Access to Shardeum Config Store which leads to create,edit,delete configurations ## Description ## Vulnerability Details I have found one endpoint which use default credentials so that attacker can bypass auth and attacker can create,edit,delete Shardeum Config Store . \##Steps to reproduce 1. Navigate to 2. use below credentials username as admin password ad password 3. you will get access to internal Dashboard there you create,edit,delete the configurations ## Impact Details attacker can bypass auth and attacker can create,edit,delete Shardeum Config Store . ## Proof of Concept ## Proof of Concept screenshot is attached. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://reports.immunefi.com/shardeum-ancillaries-ii/35157-w-and-a-insight-unauthorized-access-to-shardeum-config-store-using-default-credentials.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.