Submitted by berndartmueller
https://github.com/code-423n4/2023-01-drips/blob/9fd776b50f4be23ca038b1d0426e63a69c7a511d/src/Drips.sol#L411 
https://github.com/code-423n4/2023-01-drips/blob/9fd776b50f4be23ca038b1d0426e63a69c7a511d/src/Drips.sol#L461
Squeezing drips from a sender requires providing the sequence of drips configurations (see NatSpec description in L337-L338):
The provided history entries are hashed and verified against the senders dripsHistoryHash.
However, the sender can prevent a receiver from squeezing drips by front-running the squeeze transaction and adding a new configuration. Adding a new configuration updates the current dripsHistoryHash and invalidates the historyHash provided by the receiver when squeezing. The receiver will then fail the drips history verification in L461 and the squeeze will fail.
A sender can prevent its drip receivers from squeezing by front-running the squeeze transaction and adding a new configuration.
Drips.sol#L411
Drips.sol#L461
Consider allowing a receiver to squeeze drips from a sender up until the current timestamp.
xmxanuel (Drips) commented:
CodeSandwich (Drips) disagreed with severity and commented:
Alex the Entreprenerd (judge) commented:
