Submitted by sl1
https://github.com/code-423n4/2024-12-secondswap/blob/214849c3517eb26b31fe194bceae65cb0f52d2c0/contracts/SecondSwap_StepVesting.sol#L216-L235
As stated by the contest page, token issuer must be able to reallocate vesting allocations from one user to another. It can be done via transferVesting() function of the StepVesting contract.
SecondSwap_StepVesting.sol#L224-L232
As can be seen, the function ensures that amount transferred is not greater than amount of tokens to vest left after some of them have been claimed. 
However, it does not account for tokens that have already been vested, but remain unclaimed by a user. The moment tokens are vested, they cease to be part of the vesting process because the conditions for their release have already been met. Vested but unclaimed tokens are effectively owned by the beneficiary, but remain unclaimed. This essentially allows token issuer to transfer tokens owned by the user instead of reallocation a part of the vesting schedule.
Token issuer has an ability to transfer out tokens owner by users instead of reallocation vesting schedule.
To set up the following PoC in Foundry please follow the steps.
Inside the hardhat project directory:
Run it withforge test --match-test 'test_sl1TokenIssuerCanTransferAlreadyVestedTokens' -vv.
transferVesting() should account for tokens that have already been vested but remain unclaimed.
TechticalRAM (SecondSwap) acknowledged
