> 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/flare-fassets-or-mainnet-audit-comp/46847-sc-low-executor-fee-is-not-paid-or-burned-in-rejectinvalidredemption.md).

# #46847 \[SC-Low] executor fee is not paid or burned in \`rejectInvalidRedemption\`

**Submitted on Jun 5th 2025 at 08:47:16 UTC by @pseudoArtist for** [**Audit Comp | Flare | FAssets**](https://immunefi.com/audit-competition/audit-comp-flare-fassets)

* **Report ID:** #46847
* **Report Type:** Smart Contract
* **Report severity:** Low
* **Target:** <https://github.com/flare-foundation/fassets/blob/main/contracts/assetManager/library/RedemptionRequests.sol>
* **Impacts:**
  * Permanent freezing of funds

## Description

## Brief/Intro

When calling `rejectInvalidRedemption` the function doens't handle the executor fee correctly and doesn't call `payOrBurnExecutorFee` which will cause the fee to be stuck in the contract.

## Vulnerability Details

The function `payOrBurnExecutorFee` is called in function `rejectRedemptionRequest` which transfers the executor fee to the executor if the caller is the executor and burns the fee if it is the agent.

```solidity
    function payOrBurnExecutorFee(
        Redemption.Request storage _request
    )
        internal
    {
        uint256 executorFeeNatWei = _request.executorFeeNatGWei * Conversion.GWEI;
        if (executorFeeNatWei > 0) {
            _request.executorFeeNatGWei = 0;
            if (msg.sender == _request.executor) {
                Transfers.transferNAT(_request.executor, executorFeeNatWei);
            } else {
                Agents.burnDirectNAT(executorFeeNatWei);
            }
        }
    }
```

However the same call is not done in the function `rejectInvalidRedemption` , and later the requestID is deleted.

## Impact Details

This causes 2 problems

1. Executor fee is not burnt if the caller is agent and executors are not incentivised if they are meant to call the function.
2. The executor fee will will remain stuck in the contract as their is no function to withdraw the native tokens recieved as fee.

## References

## Proof of Concept

## Proof of Concept

Step 1: `RedemptionRequestsFacet.redeem()` is called with some executor fee.

Step 2: The function calls `RedemptionRequests.redeem()` and creates a new redemption request.

Step 3: If the address is invalid or not normalised agent calls `rejectInvalidRedemption()` and deletes redemption request without properly calling `payOrBurnExecutorFee`.

Step 4: The fee will be stuck in the contract with no way to get it.


---

# 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/flare-fassets-or-mainnet-audit-comp/46847-sc-low-executor-fee-is-not-paid-or-burned-in-rejectinvalidredemption.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.