> 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/plume-or-attackathon/52241-sc-low-unexposed-pauseable-functionality.md).

# 52241 sc low unexposed pauseable functionality

**Submitted on Aug 8th 2025 at 22:47:05 UTC by @funkornaut for** [**Attackathon | Plume Network**](https://immunefi.com/audit-competition/plume-network)

* **Report ID:** #52241
* **Report Type:** Smart Contract
* **Report severity:** Low
* **Target:** <https://github.com/immunefi-team/attackathon-plume-network-nucleus-boring-vault/blob/main/src/base/Roles/TellerWithMultiAssetSupportPredicateProxy.sol>
* **Impacts:** Contract fails to deliver promised returns, but doesn't lose value

{% hint style="info" %}
Brief/Intro

The `TellerWithMultiAssetSupportPredicateProxy` contract inherits from `Pausable` and includes pause checks, but cannot be paused because no public functions expose the internal `_pause()` and `_unpause()` methods.
{% endhint %}

## Vulnerability Details

The contract inherits `Pausable` and uses `paused()` guards in `deposit()` and `depositAndBridge()`. However, there are no externally callable `pause()` / `unpause()` functions (only the internal `_pause()` / `_unpause()` exist in `Pausable`).

Result: `paused()` is effectively always `false`, so the `if (paused()) revert` checks are unnecessary and currently wasteful. This diverges from the regular `TellerWithMultiAssetSupport` contract, which does expose `pause()` / `unpause()` and behaves correctly.

{% hint style="warning" %}
Impact

The contract can never be paused in emergencies.
{% endhint %}

## References

* <https://github.com/immunefi-team/attackathon-plume-network-nucleus-boring-vault/blob/main/src/base/Roles/TellerWithMultiAssetSupportPredicateProxy.sol?utm\\_source=immunefi#L78>
* <https://github.com/immunefi-team/attackathon-plume-network-nucleus-boring-vault/blob/main/src/base/Roles/TellerWithMultiAssetSupportPredicateProxy.sol?utm\\_source=immunefi#L78>

## Link to Proof of Concept

* <https://gist.github.com/Funkornaut/5e0d2397fea37670615c9b559d9853dd>

## Proof of Concept

{% stepper %}
{% step %}

### Steps demonstrating the issue

* The contract inherits `Pausable`.
* It never exposes the internal `_pause()` or `_unpause()` functions.
* Pause functionality is therefore broken: `paused()` remains `false`.
  {% endstep %}
  {% endstepper %}


---

# 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/plume-or-attackathon/52241-sc-low-unexposed-pauseable-functionality.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.