> 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/zerolend/29329-sc-insight-manta-aclmanager-eoa-as-emergency_admin.md).

# 29329 - \[SC - Insight] Manta ACLManager EOA as EMERGENCY\_ADMIN

Submitted on Mar 14th 2024 at 03:33:09 UTC by @mhmd\_alfa for [Boost | ZeroLend](https://immunefi.com/bounty/zerolend-boost/)

Report ID: #29329

Report type: Smart Contract

Report severity: Insight

Target: <https://pacific-explorer.manta.network/address/0xb2178109A414C3a869E5104283Fcf1a18923D0B8>

Impacts:

* Temporary freezing of funds for at least 1 hour
* Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

## Description

## Brief/Intro

An EOA 0x0f6e98a756a40dd050dc78959f45559f98d3289d has EMERGENCY\_ADMIN role. Leaked private key could lead to griefing and/or malicious halt of the protocol assets.

## Proof of Concept

1. go to <https://pacific-explorer.manta.network/address/0xb2178109a414c3a869e5104283fcf1a18923d0b8?tab=read\\_contract>
2. get EMERGENCY\_ADMIN\_ROLE = `0x5c91514091af31f62f596a314af7d5be40146b2f2355969392f055e12e0982fb`
3. inspect `hasRole(0x5c91514091af31f62f596a314af7d5be40146b2f2355969392f055e12e0982fb,0x0f6e98a756a40dd050dc78959f45559f98d3289d)` --> true


---

# 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/zerolend/29329-sc-insight-manta-aclmanager-eoa-as-emergency_admin.md?ask=<question>&goal=<user_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.
