all 9 comments

sorted by: hot top controversial new old
[–] 20 points 1 week ago (3 children)

The engineers over at Google seemingly don't give a fuck? I think a bug that effectively prevents a potential victim from calling for help should have higher priority, and most countries see it the same way, this is not a wise choice.

  • source
  • hideshow 3 child comments
  • [–] 10 points 1 week ago (2 children)

    It appears they fixed it when it was reported as another CVE?

    https://github.com/advisories/GHSA-4vm2-jjcf-2h53

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 week ago (2 children)

    How do these bugs keep happening? What could a string possibly contain to make this sort of thing crash??

  • source
  • hideshow 2 child comments
  • [–] 4 points 1 week ago* (1 child)

    Non breaking white space. There are a lot of characters in unicode that are used to get text to format correctly for Greek, or Korean, or english. The problem isnt any one language but having unicode work for every language makes it vulnrable. i.e

    ψ N̸̹͐͝ő̴̤̗͔͘ř̴̙̅m̵̢̜͉͑̌͜͝á̶̅̓͜l̵͖̔͌͗̑͝ͅ ̸̙̺͉̬̬́t̴̛͈̓e̵͚̳̊̆x̷̤͌̐t̸̯̰̘͉̑̅͒̈́͌ ̵͓̼̤̃g̴͇̥͉̊͑́̚ò̵͕̪͎́̐e̸͓͗̀̀̕s̴̜̾̈́̃͘ ̷̦̪̥̤̅h̷̨̩̝̖̃̏͠e̵͕͎̦̽̀͗̄̏ͅr̷̟̳͈̋́̚e̴̟͘͜͠ ⛥

    Although in this case its not unicode but a header in the protocol. The unicode thing was previous text sms bugs.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 1 week ago

    I hate that my mind can't get the correct context of WAP to replace what I thought it meant as a joke

  • source
  • [–] 7 points 1 week ago

    why won't Google fix it? are they stupi?

  • source