full-disclosure - Recall: Oracle read-only user can insert/update/delete data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri Apr 14 03:34:27 2006
From: eaton.lists at gmail.com (Brian Eaton)
Subject: Recall: Oracle read-only user can
	insert/update/delete data

On 4/13/06, Michael Holstein <michael.holstein@...ohio.edu> wrote:
> > In my experience, it doesn't even work in an Exchange environment. The
> > user gets a message that the message should be recalled, but the
> > original is still there, even if it hasn't been read yet. I've heard
> > people say that at one time it would auto-delete the message if it
> > hadn't been read, but I've never seen that.
>
> It does, provided you read the "recall" message first -- but since
> Outlook (by default) displays in reverse chronological order, and most
> people read email in the order received, it does little good.

Anybody understand how MS Exchange implements the "recall"
functionality?  I could see nothing in the e-mail headers that
appeared to prove the sender of the original message was the sender of
the recall request.

- Brian