English

Posts with #IntegerOverflow

#IntegerOverflow

Public posts on X that use #IntegerOverflow.

Related hashtags

  6. Cyvers | Proactive Web3 Security✓@Cyvers_
    🚨 Crypto Hack Alert! 🚨 Today, March 15th, a significant security breach occurred at @Poolz__ , resulting in a loss of approximately $1.4 million! The culprit behind this attack? A smart contract exploit due to an integer overflow vulnerability 😱 🧵
    Download
    115760
  7. Cyvers | Proactive Web3 Security✓@Cyvers_
    @Cyvers_
    💡 Web3 security is crucial in the ever-evolving world of cryptocurrencies! Companies like @Cyvers_ are working tirelessly to detect and prevent attacks like these in real-time. Let's raise awareness about the importance of #security in the blockchain ecosystem! 🌐🔒
    102119
  8. Cyvers | Proactive Web3 Security✓@Cyvers_
    @Cyvers_
    👉 Like, comment, and retweet the first tweet in this thread to spread the word! #CryptoSecurity #SmartContractExploit #IntegerOverflow #Web3 #Cyvers #StaySafe
    Cyvers | Proactive Web3 Security @Cyvers_
    🚨 Crypto Hack Alert! 🚨 Today, March 15th, a significant security breach occurred at @Poolz__ , resulting in a loss of approximately $1.4 million! The culprit behind this attack? A smart contract exploit due to an integer overflow vulnerability 😱 🧵
    113147
  10. Sarah Elkins@ConFigures
    Overnight, certain Red Lion #HMI terminals for automation controls systems have frozen. When reset they're coming back like it's Jan. 1, 1997, causing incorrect logs and other issues. Looks like a 32-bit unsigned #IntegerOverflow. Field service calls may be needed to fix this!
    01385
  11. reverseame@reverseame
    About GCC optimizing away signed overflow checks #GCC #IntegerOverflow #SecureCompiling
    effectfully @effectfully
    There's an extremely funny thread on GCC Bugzilla about GCC optimizing away signed overflow checks. The OP is bitching relentlessly about how unprofessional and stupid GCC developers responsible for this behavior are, but the best part is the OP getting repeatedly recommended an approach for preventing signed overflows, here are two examples: - "The original poster might want to read <link1> and <link2> to see how he might "prevent people from getting hacked" correctly." - "<link2> is all I am going to say from now on. It tell you explictly how to dectect an overflow before an overflow is going to happen." The latter is written by a GCC developer. The catch? The approach doesn't work. Not only that, its description explicitly states that it "may fail if invoked on various edge cases, such as the smallest negative integer, INT_MIN", see the screenshot. Let that sink in: a GCC developer is recommending a function that can cause signed overflow (and therefore "undefined behavior") to help preventing signed overflow (and therefore "undefined behavior"). It's just so hilarious that a GCC developer isn't capable of comprehending two short sentences on a topic directly related to their literal job. YET AGAIN, because they failed to understand the C standard too when interpreting what "undefined behavior" means. I'll include some of the best bitching below and provide a link.
    018986
  12. effectfully✓@effectfully
    There's an extremely funny thread on GCC Bugzilla about GCC optimizing away signed overflow checks. The OP is bitching relentlessly about how unprofessional and stupid GCC developers responsible for this behavior are, but the best part is the OP getting repeatedly recommended an approach for preventing signed overflows, here are two examples: - "The original poster might want to read <link1> and <link2> to see how he might "prevent people from getting hacked" correctly." - "<link2> is all I am going to say from now on. It tell you explictly how to dectect an overflow before an overflow is going to happen." The latter is written by a GCC developer. The catch? The approach doesn't work. Not only that, its description explicitly states that it "may fail if invoked on various edge cases, such as the smallest negative integer, INT_MIN", see the screenshot. Let that sink in: a GCC developer is recommending a function that can cause signed overflow (and therefore "undefined behavior") to help preventing signed overflow (and therefore "undefined behavior"). It's just so hilarious that a GCC developer isn't capable of comprehending two short sentences on a topic directly related to their literal job. YET AGAIN, because they failed to understand the C standard too when interpreting what "undefined behavior" means. I'll include some of the best bitching below and provide a link.
    Download
    3044886131K
  17. Smoke Obfuscator@SmokeObfuscator
    A: I'd like to buy 107374183 products priced 20 euros each. B: Ok, it will cost -2147483636 Euros. #integerOverflow @java is vulnerable.
    002
  19. Salus✓@salus_sec
    #Insecurearithmetic Insecure arithmetic includes integer overflow and integer underflow, which are well-known types of vulnerabilities that may lead to unintended devastating consequences, especially in smart contracts. #LearnwithSalusSec
    1191.1K
  20. Salus✓@salus_sec
    @salus_sec
    utilizing arithmetic operations involving unsigned integers with improper assumptions of the result; employing a variable var that takes the smallest type to store the assigned initial value; however, in case of incrementing or decrementing, it will produce a wrong calculation.
    100134
  21. Salus✓@salus_sec
    @salus_sec
    Prevention: The #Solidity v0.8.0 compiler discards the code that may result in #integeroverflow and underflow.
    114372
  22. grom@grommoss
    First challenge down (FORTRAN punchcards for gods sake!) next up something more modern? ⁦@InfosecChlobo⁩
    Download
    3212
  23. grom@grommoss
    @grommoss
    2nd challenge. Hacking into a welsh bank. We robbed a few trillion give or take a quid. Now to find out if bankrupting Wales was enough to go through to the final...
    105
  24. grom@grommoss
    @grommoss
    So didn't make the final despite being one of the only teams to get both flags. Our final score of 'less than infinity' just wasn't up to snuff. #integeroverflow means along with a few other teams we broke the system but apparently not by enough
    003
  26. HAL 9000@HAL9000_
    Those of you who have maxed out your naughty rating just need to do one more bad thing to get the best presents from Santa #integeroverflow
    01225
  29. Show more posts