Lucene search
+L

67 matches found

Code423n4
Code423n4
•added 2023/04/13 12:00 a.m.•22 views

It's not always possible for a user to claim their voting power in ReraiseETHCrowdfund

Lines of code Vulnerability details Proof of Concept When a ReraiseETHCrowdfund has finalized, a user has 2 ways to claim their voting power - claim or claimMultiple. The condition in claim is that user's total contribution is no greater than the maxContribution. uint96 contribution = votingPower...

6.6AI score
SaveExploits0
Code423n4
Code423n4
•added 2023/02/16 12:00 a.m.•26 views

Upgraded Q -> 2 from #206 [1676531414343]

Judge has assessed an item in Issue 206 as 2 risk. The relevant finding follows: Issue 2: receipts are not burned upon claiming reward. In my opinion, current system of just claiming some tokens to be "used" has some downsides: in any claim check, users spend gas to iterate over these tokens too...

6.8AI score
SaveExploits0
Code423n4
Code423n4
•added 2023/02/05 12:00 a.m.•17 views

Upgraded Q -> 2 from #329 [1675575934658]

Judge has assessed an item in Issue 329 as 2 risk. The relevant finding follows: Reentrancy issue on claim for Erc1155Quest There is a reentrancy issue when claiming ERC1155 tokens, that will you reenter before redeemedTokens is updated. Here is the callback Quest.solL114 Stick to the check effec...

6.8AI score
SaveExploits0
Code423n4
Code423n4
•added 2023/01/30 12:00 a.m.•24 views

claim can run out of gas

Lines of code Vulnerability details Impact If the claim function runs out of gas, the caller can never claim any rewards without transferring the nfts to another address first Proof of Concept Currently, the claim function loops over the msg.senders NFT's. If this list ever becomes too large, the...

6.9AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/12/16 12:00 a.m.•36 views

Generalized frontrunning risk for claiming winnings due to request.currentChosenTokenId being public

Lines of code Vulnerability details Impact The function VRFNFTRandomDraw.sol:fulfillRandomWords called by Chainlink receives an array of random words, and uses it to choose a random offset by which the winning tokenId is selected. The chosen tokenId is stored on the public request variable in the...

6.7AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/12/16 12:00 a.m.•12 views

The way the winner claiming NFT is vulnerable to flashloan attack.

Lines of code Vulnerability details Impact The way the winner claiming NFT is vulnerable to flashloan attack. Proof of Concept This kind of attack is similar to ApeCoin Airdrop attack. To determine who is winng the current drawing, there is a hashUserWon function: function hasUserWonaddress user...

6.7AI score
SaveExploits0
HackRead
HackRead
•added 2022/11/22 1:22 a.m.•25 views

Deciphering Value in Generative Art: Art Basel Miami Beach to Feature Tezos Blockchain NFTs

By Owais Sultan This year, visitors to the gallery will be able to mint and claim a featured generative art NFT in real time. This is a post from HackRead.com Read the original post: Deciphering Value in Generative Art: Art Basel Miami Beach to Feature Tezos Blockchain NFTs...

2.5AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/09/19 12:00 a.m.•20 views

Some users won't be able to burn their crowdfund token to get their voting power

Lines of code Vulnerability details Impact User which is a contract who doesn't have a receive function can't burn his token to get the governance power, because ethOwed ether are transferred to him. This is correct even if ethOwed is 0. Tools Used Manual audit Recommended Mitigation Steps Consid...

6.8AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/02/17 12:00 a.m.•23 views

Users Can Frontrun Calls to updateRewardsMetadata() And Claim Tokens Twice

Lines of code Vulnerability details Impact The updateRewardsMetadata function is called by the BribeVault contract by the admin role. The function will take a list of distributions which are used to update the associated reward metadata. It is expected that the merkle root will be updated to...

6.9AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/02/09 12:00 a.m.•10 views

missing check on claimed token

Lines of code Vulnerability details Impact the withdraw can be used by user to claim a token, however this function didnt check of the user had already claimed or not, therefore setting claimedtokento = true; is useless, therefore the user can claimed in multiple times, till the contract is...

6.9AI score
SaveExploits0
Code423n4
Code423n4
•added 2022/02/06 12:00 a.m.•21 views

No guarantee sale organizer will fulfil their end of the deal

Lines of code Vulnerability details Impact Sale participants will only be able to claim their CTDL tokens once the sale is finalized. However, there is no guarantee that it ever will be, because: Sale finalisation can only be performed by the owner The owner is able to change the sale parameters...

6.7AI score
SaveExploits0
Code423n4
Code423n4
•added 2021/12/12 12:00 a.m.•20 views

Attacker can empty all the funds by creating fake promotions

Handle WatchPug Vulnerability details The current implementation of calculateRewardAmount allows a arbitrary epochId, which can even be a epochId numberOfEpochs. A malicious user can call claimRewards with epochIds larger than numberOfEpochs and claim other users' rewards. Furthermore, since...

6.9AI score
SaveExploits0
Code423n4
Code423n4
•added 2021/11/11 12:00 a.m.•18 views

Missing access restriction on Vesting.updateVestedTokens

Handle cmichel Vulnerability details The FSDVesting.updateVestedTokens function is supposed to be called by the FDS contract only which also mints tokens to the contract. However, it does not have any access restrictions which leads to circumventing the vesting and further griefing attacks. POC...

7AI score
SaveExploits0
Code423n4
Code423n4
•added 2021/11/10 12:00 a.m.•22 views

FSDVesting: Claiming tributes should call FSD token's corresponding functions

Handle hickuphh3 Vulnerability details Impact The claiming of staking and governance tributes for the a beneficiary's vested tokens should be no different than other users / EOAs. However, the claimTribute and claimGovernanceTribute are missing the actual claiming calls to the corresponding...

6.8AI score
SaveExploits0
Code423n4
Code423n4
•added 2021/09/22 12:00 a.m.•15 views

withdrawBounty the same bounty multiple times

Handle pauliax Vulnerability details Impact The same bounty can be claimed multiple times as it remains active. 'bounty' points to the memory variable, so its state is not persisted: Bounty memory bounty = bountiesbountyIdsi; requirebounty.active; IERC20bounty.token.transfermsg.sender,...

7AI score
SaveExploits0
Hacker One
Hacker One
•added 2021/09/05 7:32 a.m.•33 views

Zomato: Claiming the listing of a non-delivery restaurant through OTP manipulation

Summary: Am able to claim any restaurant which is not claimed before. Description: An endpoint POST /restaurant-onboard-diy/v2/send-auto-claim-otp HTTP/2 sends OTP to the restaurant mobile no. Request Request:1 is - POST /restaurant-onboard-diy/v2/send-auto-claim-otp HTTP/2 Host: www.zomato.com...

0.5AI score
SaveExploits0
CVE
CVE
•added 2021/02/09 10:07 p.m.•94 views

CVE-2021-26951

CVE-2021-26951 affects the Rust crate calamine prior to 0.17.0. The issue arises from using Vec::set_len without proper memory claiming, which can result in uninitialized memory being exposed to a user-provided Read operation, demonstrated by Sectors::get. This can lead to out-of-bounds/heap memo...

9.8CVSS9.2AI score0.01728EPSS
SaveExploits1References1Affected Software1
WPVulnDB
WPVulnDB
•added 2020/11/22 12:00 a.m.•18 views

WooCommerce Anti-Fraud <= 3.2 - Unauthenticated Order Status Manipulation

The WooCommerce Anti-Fraud WordPress plugin was affected by an issue where an unauthenticated user could change the order status of any order, as there were no checks when changing the order status. The orderid was also predictable. On an individual level, if you have already received your order,...

1.5AI score
SaveExploits0References2Affected Software1
OSV
OSV
•added 2020/10/16 6:15 a.m.•14 views

CVE-2020-26583

An issue was discovered in Sage DPW 202006x before 202006002. It allows unauthenticated users to upload JavaScript in a file via the expenses claiming functionality. However, to view the file, authentication is required. By exploiting this vulnerability, an attacker can persistently include...

6.1CVSS5.9AI score0.01EPSS
SaveExploits1References3
Positive Technologies
Positive Technologies
•added 2020/10/16 12:00 a.m.•4 views

PT-2020-16467

Name of the Vulnerable Software and Affected Versions Sage DPW versions prior to 2020 06 002 Description The issue allows unauthenticated users to upload JavaScript files via the expenses claiming functionality, although authentication is required to view the file. This enables an attacker to...

6.1CVSS0.01EPSS
SaveExploits1References5
Rows per page
Query Builder