``` TypeError: Cannot read properties of null (reading 'C') at Ccf ( https://docs.google.com/static/document/client/js/157553674-... ) at Bcf ( https://docs.google.com/static/document/client/js/157553674-... ) ``` Has something to do with grammar. The document does not fail when `Show grammar suggestion` is turned off.
does it talk to a grammar check api endpoint or is it done locally?
would be funny if it were a remotely exploitable bug in an api endpoint.
Here's a bug I discovered in MS Word in 2004, which has survived the past 18 years of updates and is even present in the web version: https://1drv.ms/w/s!AgYiBqBjIZZpfkcvO9jnOel9T2o?e=tFA4wp If you join the two lines using a backspace at the start of the second line, the second line turns into gibberish.
How did you create the document? When I hit backspace it does "turn into gibberish", but because it seems to inherit the type choices from the ether between the two lines to put it into Wingdings in red with italic and strikethrough. Did you create that type setting?
``` TypeError: Cannot read properties of null (reading 'C') at Ccf ( https://docs.google.com/static/document/client/js/157553674-... ) at Bcf ( https://docs.google.com/static/document/client/js/157553674-... ) ``` Has something to do with grammar. The document does not fail when `Show grammar suggestion` is turned off.
Probably just getting triggering excessive backtracking on some regex.
When I come across posts like these, I just wonder, "How in the world did the user discover this in the first place?!" Let's place bets: A) The user just let autocomplete "take it away" (not sure about this one since they were able to access the console) B) Pen Testing? C) Error copy and pasting? D) Actual dialog in a sci-fi post-apocalyptic love story where a robot discovers the Turing test and attempts to set itsel…
Some more options: Just a demonstration of how Ctrl-C, Ctrl-V works. Literal transcript of a stammered conversation. Poetry / word-based art.
Once a customer was able to destroy an old ES cluster because they copy pasted some text from a PDF into a search box ... that text got sent directly to the ES cluster without much escaping ... there were lots of "*" in there. The query complexity exploded, ES ran out of memory, and the index got corrupted and I don't remember why, it could not recover. We had to re-index all the data. Lots of fun. Lesson learned: pr…
Maybe escaping the character wouldn't help if every * is telling the server to process a long loop, but some max range or time to perform the task. I can't tell which company, but I managed to do exactly that you described a few months ago, with a valid query, and it's one of those companies you can guess if I tell you the first letter of its name.
Years ago in school, maybe about 1992 or so, I managed to make xdm (X Display Manager) crash and dump me a root window by simply holding down a key until the buffer ran out. I remember wondering how anybody didn't discover this before me. Similar behavior with the university phone system (repeatedly pressing '0') eventually dropped me an outside line that I didn't have to pay for (yes, for you young folks, we used to…