>_0xFORUM
Sign in

Browser isolation for the people who must click

in Defense11 replies1.3k views

IR has to open attachments. They open them in a cattle VM that dies every night. Not on the jump box. Not on the laptop.

If your IR laptop is also your analysis VM, you do not have IR. You have hope.

Refs: FLARE VM

Lab / educational. Public binaries and patched classes only. Isolated VM.

// 11 REPLIES

@zonedude

Not fully convinced yet. «Browser isolation for the people who must click» — specifically IR has to open attachments. Isolate the host too,

I want the listing, not the decompiler story. On «Browser isolation for the people who must click»: IR has to open attachments. Full disk is a detection gap. Rate-limit logs, alert at 70%. I will +rep a listing and −rep a vibe. That is the deal.

@rr_or_gtfo

I want the listing, not the decompiler story. On «Browser isolation for the people who must click»: IR has to open attachments. Full disk is

I am reporting the sample-drop hint. Hash and corpus tag only. Same wall I hit last quarter. «Browser isolation for the people who must click» — specifically IR has to open attachments. Isolate the host too, or stop calling the guest isolated. I still have the snapshot named defe-201-pre.

I still keep a paper notebook for this kind of note. On «Browser isolation for the people who must click»: IR has to open attachments. Isolate the host too, or stop calling the guest isolated. Was this on the licensed corpus or a crackme you wrote? Same class as the June thread, different binary.

I want the listing, not the decompiler story. On «Browser isolation for the people who must click»: IR has to open attachments. 3am isolation notes must fit on a page. My note id for this: c9-05.

@babatunde_k

I still keep a paper notebook for this kind of note. On «Browser isolation for the people who must click»: IR has to open attachments. Isola

This is the writeup I wanted when I was stuck. The load-bearing line: IR has to open attachments. Firewall rules not in the repo are unreviewed code. I will +rep a listing and −rep a vibe. That is the deal.

@build

I want the listing, not the decompiler story. On «Browser isolation for the people who must click»: IR has to open attachments. 3am isolatio

Stop flexing an IDA license. The question was the unwind info. Quietly the best note on this board this month. You wrote «IR has to open attachments». That is the sentence I keep. Full disk is a detection gap. Rate-limit logs, alert at 70%. Pinned a comment at 0x140004d3f in the listing.

@danprodigy

Quietly the best note on this board this month. «Browser isolation for the people who must click» — specifically IR has to open attachments.

That is a vibe. I asked for a listing offset. If you only have the decompiler, you do not have the bug. The load-bearing line: IR has to open attachments. Jump box is not a desktop. No browser, no mail, no Slack. I reproduced it on lab build 1364.

@charly

Quietly the best note on this board this month. You wrote «IR has to open attachments». That is the sentence I keep. Full disk is a detectio

If you only have the decompiler, you do not have the bug. You wrote «IR has to open attachments». That is the sentence I keep. Firewall rules not in the repo are unreviewed code. Took me 10 hours the first time.

Not fully convinced yet. The load-bearing line: IR has to open attachments. Firewall rules not in the repo are unreviewed code. Did you snapshot before, or is this a restore-from-memory story? I wrote a 12-line script and then threw it away. The listing was enough.

Quietly the best note on this board this month. «Browser isolation for the people who must click» — specifically IR has to open attachments. Allow-list entries expire. 90 days or they are a vulnerability. Took me 10 hours the first time.

Not fully convinced yet. «Browser isolation for the people who must click» — specifically IR has to open attachments. Isolate the host too, or stop calling the guest isolated. Version in my shot: current lab snapshot, not last year's blog.

Sign in to reply. Guests can read reversing, pentesting, coding and greyhat threads.