exploit dosent work/patched

[dekid69]

The insecurely exploit is patched since my school changed the securely version and extension ID, they forced install by not using the Chrome web store, and the ID is "knneimmpeamikmjijmnhjmmobddleohj"

If you don't want to make a patch for my school @zek-c how can I create an HTML file with the cookie to corrupt securely's cookies

[zek-c]

ok so insecurly is slowly getting patched out and i am NOT making a patch. an html file can't run the cookie corrupter because javascript doesn't allow a different tab to set a cookie for a different URL. you have to be able to run javascript on securly.com. skiovox is also getting patched out, so you'll have to wait it out. you can also use the terminal exploit which i will post here maybe in a while but im lazy rn cus it's winter break

[dekid69]

The JavaScript dosent work for me since it dosent do anything on securely.com

Although how can you create the cookie though, since I’m thinking to make it by using code pen

On Fri, Jan 5, 2024 at 3:06 PM zek @.***> wrote:

Closed #47 https://github.com/zek-c/Securly-Kill-V111/issues/47 as completed.

— Reply to this email directly, view it on GitHub https://github.com/zek-c/Securly-Kill-V111/issues/47#event-11405908476, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVPQCXPEEAAT5FMWCDGJMJTYNCBOBAVCNFSM6AAAAABBOY3SLKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGQYDKOJQHA2DONQ . You are receiving this because you authored the thread.Message ID: @.***>

[zek-c]

the javascript doesn't do anything because javascript bookmarklets and URL running is disabled after V116. making a cookie is easy, just document.cookie =${parameters};

[zek-c]

here's a site you can get started with cookies; https://www.w3schools.com/js/js_cookies.asp; unfortunately it's no easy task to load corrupted cookies and you have to examine securly source:

[dekid69]

Then how did you made the currupted cookies?

On Fri, Jan 5, 2024 at 3:26 PM zek @.***> wrote:

here's a site you can get started with cookies; https://www.w3schools.com/js/js_cookies.asp; unfortunately it's no easy task to load corrupted cookies and you have to examine securly source:

— Reply to this email directly, view it on GitHub https://github.com/zek-c/Securly-Kill-V111/issues/47#issuecomment-1879376352, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVPQCXOYSUOIIKD4VT2A463YNCDZ7AVCNFSM6AAAAABBOY3SLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGM3TMMZVGI . You are receiving this because you authored the thread.Message ID: @.***>

[zek-c]

it just replaces securlys current cookies with false cookies that don't actively search for blocked sites and blocks the cdn n stuff and corrupts the connection.

[dekid69]

@zek-c yea i know how that works, but how did you create the currupted cookies, did you use a converter or something?

[zek-c]

uh no i gave it bad attributes and malbytes, messes with securlys functions

[dekid69]

@zek-c then how did you convert that into a cookie?

[zek-c]

by giving the attributes to the cookie, a cookie is just javascript that runs every time you open a page so just set the cookie withthe attributes with document.cookie='{attributes here}'