[Full-disclosure] JSPWiki Multiple Input Validation Vulnerabilities

JSPWiki Multiple Input Validation Vulnerabilities Application: JSPWiki Version: 2.4.103 and 2.5.139 BID: 25803 Credit: Jason Kratzer Date: 9/24/2007 Background JSPWiki is wiki software built around the standard J2EE components of

Re: [Full-disclosure] defining 0day

This make sense,but if we can't even agree on what the public perceives as a threat that they know nothing about,until a patch comes out or a full blown exploit shows up ITW (such trivial bullshit),how can we even say that we agree on the terms like disclosure,vulnerability,etc,etc,etc. How about

Re: [Full-disclosure] defining 0day

Catch a good belly laugh with Steve Shockley's response to Thor(Hammer of God) over on Bugtraq. Cheers, Scott [EMAIL PROTECTED] wrote: > The game king of the hill comes to mind watching this. Who will stand alone > on top with all others bowing down before him? > > Geoff > > Sent from my Black

[Full-disclosure] [USN-520-1] fetchmail vulnerabilities

=== Ubuntu Security Notice USN-520-1 September 26, 2007 fetchmail vulnerabilities CVE-2007-1558, CVE-2007-4565 === A security issue affects the following Ubuntu releases: Ubunt

Re: [Full-disclosure] defining 0day

The game king of the hill comes to mind watching this. Who will stand alone on top with all others bowing down before him? Geoff Sent from my BlackBerry wireless handheld. -Original Message- From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Date: Tue, 25 Sep 2007 21:04:24 To:full-disclos

Re: [Full-disclosure] defining 0day

How many days has this RIDICULOUS argument been raging, apparently without ANYBODY here mentioning the Medical background of Zero Day? Patient Zero? Any of this ringing a bell? Not that it matters. The other thing I have yet to see is an explanation of why this particular bout of mental masturbatio

Re: [Full-disclosure] Full-Disclosure Definition of 0Day

> -- > > Message: 3 > Date: Tue, 25 Sep 2007 14:02:27 -0500 (CDT) > From: Gadi Evron <[EMAIL PROTECTED]> > > Okay. I think we exhausted the different views, and maybe we are now able > to come to a conlusion on what we WANT 0day to mean. > > What do you, as profess

Re: [Full-disclosure] defining 0day

> What do you, as professional, believe 0day should mean, > regardless of previous definitions? I think there is some slight residual usefulness to designating vulnerabilities whose first public disclosure results from discovery/analysis of an active exploit already "in the wild". ("0 days" th

Re: [Full-disclosure] 0-day inquiry

Actually, nine thousand Euro for an IIS6 exploit seems too low. Let's call it off for now. By the way, is this a 0day bug or 0day exploit or public 0day or private patched exploit 0day 0day? Gadi can help you out with this classification as he is an expert in computer hacking. J On Tue, 25 Se

Re: [Full-disclosure] defining 0day

0day means vulnerability which was never used IRL, or use 0 time, thats why we use term 0day. But 0day doesnt mean it's an new type of vulnerability, otherwise the appopriate term should be 0-vulnerability. ___ Full-Disclosure - We believe in it. Charter

Re: [Full-disclosure] defining 0day

0day means vulnerability which was never used IRL, or use 0 time, thats why we use term 0day. But 0day doesnt mean it's an new type of vulnerability, otherwise the appopriate term should be 0-vulnerability. On 9/25/07, Gadi Evron <[EMAIL PROTECTED]> wrote: > > On Tue, 25 Sep 2007, Thor (Hammer of

Re: [Full-disclosure] defining 0day

I asked a few fairly regular Joes (our sales staff) what 0Day means to them.. just the words, they have no point of reference and they all pretty much agreed that they thought it meant "less than a day old" "or less than 24 hours ago, X happened" that is what i remember it being in the old NNTP

Re: [Full-disclosure] defining 0day

On Wed, 26 Sep 2007, Charles Miller wrote: > On 26/09/2007, at 5:02 AM, Gadi Evron wrote: > >> Okay. I think we exhausted the different views, and maybe we are now able >> to come to a conlusion on what we WANT 0day to mean. >> >> What do you, as professional, believe 0day should mean, regardless

Re: [Full-disclosure] defining 0day

On 9/25/07, Adrian Griffis <[EMAIL PROTECTED]> wrote: > I understand why this descriptivist approach is tempting over a > prescriptivist approach. But it's important, I think, to keep in mind > that the public uses the word "illegal" when they really mean > "unlawful" and uses the word "Schizophr

Re: [Full-disclosure] defining 0day

On 26/09/2007, at 5:02 AM, Gadi Evron wrote: > Okay. I think we exhausted the different views, and maybe we are > now able to come to a conlusion on what we WANT 0day to mean. > > What do you, as professional, believe 0day should mean, regardless > of previous definitions? As a professional,

Re: [Full-disclosure] defining 0day

On 9/25/07, Brian Loe <[EMAIL PROTECTED]> wrote: > On 9/25/07, Gadi Evron <[EMAIL PROTECTED]> wrote: > > No longer good enough. > > > > We can get a press scare over a public vuln release, or a wake-up call. > > > > I think we can do better as an industry. > > Who, then, rewrites all of the referen

Re: [Full-disclosure] CORE-2007-0817: Remote Command execution, HTML and JavaScript injection vulnerabilities in AOL's Instant Messaging software

Hi, Version 6.5.3.12 is still vulnerable. The only good solution I see here is that AOL will lock down Local Zone. Ready, AIM, fire! http://aviv.raffon.net/2007/09/25/ReadyAIMFire.aspx --Aviv. -Original Message- From: Core Security Technologies Advisories [mailto:[EMAIL PROTECTED] Sen

Re: [Full-disclosure] 0-day inquiry

You refuse any test, I propose a price and you seems its too slow... Is it for that its a fake ? Let me test it for you for information : this phone number is down, and it's not my real name/city/country... You already mailed for other 0day request and you already joke from me on full-disclosure,

[Full-disclosure] [USN-519-1] elinks vulnerability

=== Ubuntu Security Notice USN-519-1 September 25, 2007 elinks vulnerability CVE-2007-5034 === A security issue affects the following Ubuntu releases: Ubuntu 6.06 LTS Ubuntu 6.

Re: [Full-disclosure] CN spam links in Google and Yahoo

If you run a blog you can see easily why these sites are indexed! I get hundreds of spam comments from them! On 9/25/07, blah <[EMAIL PROTECTED]> wrote: > > Read your SANS diary daily! > > http://isc.sans.org/diary.html?storyid=3408 > > Spammers feeling lucky with Google > Published: 2007-09-21, >

Re: [Full-disclosure] CN spam links in Google and Yahoo

Read your SANS diary daily! http://isc.sans.org/diary.html?storyid=3408 Spammers feeling lucky with Google Published: 2007-09-21, Last Updated: 2007-09-21 07:31:49 UTC by Bojan Zdrnja (Version: 2) For quite some time spammers have been trying to hide links advertised in their e-mails. The main

Re: [Full-disclosure] defining 0day

At what point does it honestly matter? The term will be used however it is seen fit to use by the person using it. Trying to redefine it how you see fit or recast it into what you believe is just waisting time and effort. Why not do something useful? This debate takes the same turn of event

Re: [Full-disclosure] defining 0day

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > No longer good enough. > > We can get a press scare over a public vuln release, or a wake-up call. > > I think we can do better as an industry. > "Zero Day" is the day I could give two shits about this thread. D -BEGIN PGP SIGNATURE- Vers

Re: [Full-disclosure] 0day: PDF pwns Windows

Daylight come and me wanna go home... This one time, at band camp, Thor (Hammer of God) wrote: > For the record, the original term "O-Day" was coined by a dyslexic > security engineer who listened to too much Harry Belafonte while working > all night on a drink of rum. It's true. Really. > > t

Re: [Full-disclosure] defining 0day

On 9/25/07, Gadi Evron <[EMAIL PROTECTED]> wrote: > No longer good enough. > > We can get a press scare over a public vuln release, or a wake-up call. > > I think we can do better as an industry. > Who, then, rewrites all of the reference material? And doesn't any new definition simply become def

Re: [Full-disclosure] defining 0day

On Tue, 25 Sep 2007, Brian Loe wrote: > On 9/25/07, Gadi Evron <[EMAIL PROTECTED]> wrote: > >> Okay. I think we exhausted the different views, and maybe we are now able >> to come to a conlusion on what we WANT 0day to mean. >> >> What do you, as professional, believe 0day should mean, regardless o

Re: [Full-disclosure] defining 0day

On 9/25/07, Gadi Evron <[EMAIL PROTECTED]> wrote: > Okay. I think we exhausted the different views, and maybe we are now able > to come to a conlusion on what we WANT 0day to mean. > > What do you, as professional, believe 0day should mean, regardless of > previous definitions? Seems to me that

Re: [Full-disclosure] 0day: PDF pwns Windows

That was a dumb fucking joke. Please end this thread. J On Tue, 25 Sep 2007 14:39:24 -0400 "Thor (Hammer of God)" <[EMAIL PROTECTED]> wrote: >For the record, the original term "O-Day" was coined by a dyslexic >security engineer who listened to too much Harry Belafonte while >working >all night

[Full-disclosure] defining 0day

On Tue, 25 Sep 2007, Thor (Hammer of God) wrote: > For the record, the original term "O-Day" was coined by a dyslexic > security engineer who listened to too much Harry Belafonte while working > all night on a drink of rum. It's true. Really. > > t Okay. I think we exhausted the different views,

[Full-disclosure] defining 0day

On Tue, 25 Sep 2007, Thor (Hammer of God) wrote: > For the record, the original term "O-Day" was coined by a dyslexic > security engineer who listened to too much Harry Belafonte while working > all night on a drink of rum. It's true. Really. > > t Okay. I think we exhausted the different views,

Re: [Full-disclosure] 0day: PDF pwns Windows

For the record, the original term "O-Day" was coined by a dyslexic security engineer who listened to too much Harry Belafonte while working all night on a drink of rum. It's true. Really. t > -Original Message- > From: Roland Kuhn [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 25

Re: [Full-disclosure] 0day: PDF pwns Windows

On 25 Sep 2007, at 00:57, Lamont Granquist wrote: The exploit is not made public by its use. The exploit is not even made public by (back-channel) sharing amongst the hacker/cracker community. The exploit is only made public if detected or the vulnerability is disclosed. Until detected/di

Re: [Full-disclosure] CORE-2007-0817: Remote Command execution, HTML and JavaScript injection vulnerabilities in AOL's Instant Messaging software

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Holy shit, your timeline has more entries than Anne Frank's diary! On Tue, 25 Sep 2007 12:20:55 -0400 Core Security Technologies Advisories <[EMAIL PROTECTED]> wrote: >Core Security Technologies – CoreLabs Advisory > http://www.coresecurity.

[Full-disclosure] CN spam links in Google and Yahoo

http://news.yahoo.com/s/zd/20070924/tc_zd/215816 I've seen this a lot lately, and I don't see how these sites were allowed. Is there anyone here who can shed some light on this? Steve Excerpt: "A reader, Courtney Cox (no relation to the actress), recently pointed out to me that the top results

Re: [Full-disclosure] 0day: PDF pwns Windows

Nice, sounds almost exactly like what I said a few days ago. Good to see the bullet-proof wikipedia has my back. Steven www.securityzone.org > > http://en.wikipedia.org/wiki/0day > > > /thread > > --=Q=-- > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] O

[Full-disclosure] 0-day inquiry

Hi, still selling 0day for Windows (IIS, Apache, Office) and UNIX (some daemon) ___ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/

Re: [Full-disclosure] 0day: PDF pwns Windows

http://en.wikipedia.org/wiki/0day /thread --=Q=--   -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Sent: Tuesday, September 25, 2007 11:55 AM To: J. Oquendo Cc: Chad Perrin; pdp (architect); Gadi Evron; [EMAIL PROTECTED]; full-disclosure@lists

[Full-disclosure] [ MDKSA-2007:188 ] - Updated postgresql packages prevent access abuse using dblink

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ___ Mandriva Linux Security Advisory MDKSA-2007:188 http://www.mandriva.com/security/ ___

Re: [Full-disclosure] 0day: PDF pwns Windows

J. Oquendo wrote: > Jason wrote: > >> You present a valid position but fall short of seeing the whole picture. > >> As an attacker, nation state or otherwise, my goal being to cripple >> communications, 0day is the way to go. Resource exhaustion takes >> resources, something the 0day can depriv

Re: [Full-disclosure] 0day: PDF pwns Windows

Hi Crispin, I agree with almost everything you say until here: "I continue to dismiss the requirement that an 0day be found maliciously exploiting machines, because that requires inferring intent." IMO, everybody in this thread is taking this from an inside-to-outside approach, whereas a '0day'

[Full-disclosure] SimpNews version 2.41.03 File Content Disclosure Vulnerability

netVigilance Security Advisory #69 SimpNews version 2.41.03 File Content Disclosure Vulnerability Description: SimpNews is a news system written in PHP. Features: Data stored in MySQL, admin interface, support for multiple languages, support for multiple instances in one database, own header, mul

[Full-disclosure] SimpGB version 1.46.02 Multiple XSS Attack Vulnerabilities

netVigilance Security Advisory #67 SimpGB version 1.46.02 Multiple XSS Attack Vulnerabilities Description: SimpGB is a guestbook with data stored in MySQL, administration interface and support for multiple languages. Features: Data stored in MySQL, Administration interface, Support for multiple

[Full-disclosure] SimpGB version 1.46.02 Multiple Path Disclosure Vulnerabilities

netVigilance Security Advisory #64 SimpGB version 1.46.02 Multiple Path Disclosure Vulnerabilities Description: SimpGB is a guestbook with data stored in MySQL, administration interface and support for multiple languages. Features: Data stored in MySQL, Administration interface, Support for multi

[Full-disclosure] SimpNews version 2.41.03 Multiple XSS Attack Vulnerabilities

netVigilance Security Advisory #70 SimpNews version 2.41.03 Multiple XSS Attack Vulnerabilities Description: SimpNews is a news system written in PHP. Features: Data stored in MySQL, admin interface, support for multiple languages, support for multiple instances in one database, own header, multi

[Full-disclosure] SimpNews version 2.41.03 Multiple Path Disclosure Vulnerabilities

netVigilance Security Advisory #68 SimpNews version 2.41.03 Multiple Path Disclosure Vulnerabilities Description: SimpNews is a news system written in PHP. Features: Data stored in MySQL, admin interface, support for multiple languages, support for multiple instances in one database, own header,

[Full-disclosure] SimpGB version 1.46.02 Information Disclosure Vulnerability

netVigilance Security Advisory #66 SimpGB version 1.46.02 Information Disclosure Vulnerability Description: SimpGB is a guestbook with data stored in MySQL, administration interface and support for multiple languages. Features: Data stored in MySQL, Administration interface, Support for multiple

[Full-disclosure] SimpGB version 1.46.02 File Content Disclosure Vulnerability

netVigilance Security Advisory #65 SimpGB version 1.46.02 File Content Disclosure Vulnerability Description: SimpGB is a guestbook with data stored in MySQL, administration interface and support for multiple languages. Features: Data stored in MySQL, Administration interface, Support for multiple

[Full-disclosure] CORE-2007-0817: Remote Command execution, HTML and JavaScript injection vulnerabilities in AOL's Instant Messaging software

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Core Security Technologies – CoreLabs Advisory http://www.coresecurity.com/corelabs Remote command execution, HTML and JavaScript injection vulnerabilities in AOL’s Instant Messaging software *Advisory Information* Title: Remote

Re: [Full-disclosure] 0day: PDF pwns Windows

On Tue, 25 Sep 2007, J. Oquendo wrote: > In a strategic war, most countries aim to eliminate supply points and > mission critical infrastructure as quickly as possible. In a > cyberwarfare situation me personally, I would aim to 1) disrupt/stop via > a coordinated attack whether its via a botnet or

Re: [Full-disclosure] 0day: PDF pwns Windows

On Tue, 25 Sep 2007, Jason wrote: > You present a valid position but fall short of seeing the whole picture. > > As an attacker, nation state or otherwise, my goal being to cripple > communications, 0day is the way to go. Resource exhaustion takes > resources, something the 0day can deprive the ene

[Full-disclosure] rPSA-2007-0199-1 openssl openssl-scripts

rPath Security Advisory: 2007-0199-1 Published: 2007-09-25 Products: rPath Linux 1 Rating: Major Exposure Level Classification: Remote Deterministic Unauthorized Access Updated Versions: openssl=/[EMAIL PROTECTED]:devel//1-compat/0.9.7a-0.1-1 openssl-scripts=/[EMAIL PROTECTED]:devel//1-

[Full-disclosure] iDefense Security Advisory 09.25.07: Linux Kernel ALSA snd_mem_proc_read Information Disclosure Vulnerability

Linux Kernel ALSA snd_mem_proc_read Information Disclosure Vulnerability iDefense Security Advisory 09.25.07 http://labs.idefense.com/intelligence/vulnerabilities/ Sep 25, 2007 I. BACKGROUND Linux is a clone of the UNIX operating system, written from scratch by Linus Torvalds with assistance fro

Re: [Full-disclosure] 0day: PDF pwns Windows

On Tue, 25 Sep 2007 10:48:22 EDT, "J. Oquendo" said: > Counterpoint... You're trying to shoot me down with 0day crap: > > You --> 0day attack --> My Infrastructure > > Me --> Botnet --> Your infrastructure > > Never having to consume any resources other than a point and click shoot > em up atta

Re: [Full-disclosure] 0day: PDF pwns Windows

Jason wrote: > You present a valid position but fall short of seeing the whole picture. > As an attacker, nation state or otherwise, my goal being to cripple > communications, 0day is the way to go. Resource exhaustion takes > resources, something the 0day can deprive the enemy of. Counterpoint.

Re: [Full-disclosure] 0day: PDF pwns Windows

J. Oquendo wrote: > Crispin Cowan wrote: > >> This is a perfectly viable way to produce what amounts to Internet >> munitions. The recent incident of Estonia Under *Russian Cyber Attack*? >> is an example >> of such a network brush war i

Re: [Full-disclosure] 0day: PDF pwns Windows

Crispin Cowan wrote: > > This is a perfectly viable way to produce what amounts to Internet > munitions. The recent incident of Estonia Under *Russian Cyber Attack*? > is an example > of such a network brush war in which possession of such

Re: [Full-disclosure] 0day: PDF pwns Windows

Minor point: No need to limit such accumulations to nation-states though. People interested in fiddling with other peoples' computers have come up with attacks that don't get instantly published at least since the 1970s, and have had more-or-less private channels to communicate them. The motives

Re: [Full-disclosure] 0day: PDF pwns Windows

On Sun, 23 Sep 2007, Chad Perrin wrote: > In the case of that "private zero day exploit", then, nobody will ever > know about it except the person that has it waiting in reserve -- and if > someone else discovers and patches the vulnerability before the exploit > is ever used, it never becomes a

Re: [Full-disclosure] 0day: PDF pwns Windows

Chad Perrin wrote: > On Sat, Sep 22, 2007 at 10:34:07PM -0700, Crispin Cowan wrote: > >> A "private 0day exploit" (the case I was concerned with) would be where >> someone develops an exploit, but does not deploy or publish it, holding >> it in reserve to attack others at the time of their choos

Re: [Full-disclosure] 0day: PDF pwns Windows

On Sat, Sep 22, 2007 at 10:34:07PM -0700, Crispin Cowan wrote: > > A "private 0day exploit" (the case I was concerned with) would be where > someone develops an exploit, but does not deploy or publish it, holding > it in reserve to attack others at the time of their choosing. Presumably > if such

[Full-disclosure] rPSA-2007-0198-1 kernel

rPath Security Advisory: 2007-0198-1 Published: 2007-09-24 Products: rPath Linux 1 Rating: Critical Exposure Level Classification: Local Root Deterministic Privilege Escalation Updated Versions: kernel=/[EMAIL PROTECTED]:devel//1/2.6.22.7-0.1-1 rPath Issue Tracking System: https://issu

Re: [Full-disclosure] 0day: PDF pwns Windows

yes I believe the vuls will most from the JS feature, and we (Fortinet Security Research Team) has finished our security review on Adobe Reader/Acrobat, with the vendor's process, we will release advisories some months too, expecting it! welcome to my blog: http://ruder.cdut.net From: "

[Full-disclosure] Fwd: gnucitizen 0day

-- Forwarded message -- From: worried security <[EMAIL PROTECTED]> Date: Sep 25, 2007 9:15 AM Subject: gnucitizen 0day To: [EMAIL PROTECTED] On 9/20/07, pdp (architect) <[EMAIL PROTECTED]> wrote: > > http://www.gnucitizen.org/blog/0day-pdf-pwns-windows When you do your full write

[Full-disclosure] www.archive.org <--- XSS (and under attack)

Hello: I could take a while to investigate this more but I have no time ATM (veeery busy) and the website is under attack. (should be a matter to try that script on some form. Get a virtual pass for the library, digg in the book publishing forms and report back) Try this links: http://www.archive