Suggestion : Providing the DATE for exploits

[tnagareshwar at gmail.com (Nagareshwar Talekar)]

Hi Moore...

After going through the source code i found out where to make the changes to
incorporate date field....

These are the places where the changes have to be done.
-----------------------------------------------------------------------------------------
1) File : \home\framework\lib\Msf\module.pm
$a=> New line is added to the my $defaults ={
....
'BirthDate' => 'Unknown',
...

}
--------------------------------------------------------------------------------------------
$b => Under "# Generic Accessors" new sub function is added
sub BirthDate { my $self = shift; return($self->Info->{'BirthDate'}); }

--------------------------------------------------------------------------------------------

2) File : \home\framework\lib\Msf\textui.pm

$a => Modified the function "DumpExploits "
For loop is modified to show the date field after the $mod_file field.

foreach my $mod_file (sort keys %{$exploits}) {
my $mod_class = $exploits->{$mod_file}->ModuleClass;
my $mod_name = $exploits->{$mod_file}->Name;
my $mod_date = $exploits->{$mod_file}->BirthDate;


# Only display modules belonging to this class
if ($class) {
next if $class ne $mod_class;
$col->AddRow($mod_file, $mod_date, $mod_name);
}
# Otherwise display all exploits and a column with the class identifier
else {
$col->AddRow($mod_file, $mod_date, $mod_name);
}
}

---------------------------------------------------------------------------------------------

$b => Modified function "DumpExploitSummary"
New line is added to show the date field for the exploit
 $output .= ' BirthDate: ' . $exploit->BirthDate . "\n";

----------------------------------------------------------------------------------------------
3) Exploit module has to be updated
All the previous exploit module should have one more field under my $info =
 'BirthDate' => '' 1-10-2005',
Any new exploit developer , just have to include this field in their module.
----------------------------------------------------------------------------------------------

Let me know if there are any changes to be done apart from that..

Now the question is to add the updated files to new database. If any
developer is willing to do this then this information will be helpful to
them. Otherwise i can takeup the task...

Thank you.



On 10/3/05, Nagareshwar Talekar <tnagareshwar at gmail.com> wrote:
> Hi all,
>
> Currently there are hundred exploits ( Congrats to MSF team for century
> :-) ). And it will
> not be difficult to add up the date. I have not seen the source code. We
> need one more additional field for tracking up date.
>
> If there are no takers...i can take up the work...
>
> Thanks
>
>
> On 10/3/05, H D Moore <hdm at metasploit.com > wrote:
> > Since the OSVDB [osvdb.org <http://osvdb.org>] already tracks the
> > vulnerability disclosure
> > date, all we need to do is add the appropriate references and write an
> > auto-retrieval system. Does anyone have a strong reason for tracking the
> > module release date as well?
> >
> > -HD
> >
> > On Sunday 02 October 2005 13:48, H D Moore wrote:
> > > Unless someone volunteers to create and maintain this information for
> > > the entire exploit set, it probably won't end up in a release. Any
> > > takers?
> > >
> > > -HD
> > >
> > > On Sunday 02 October 2005 12:14, Nagareshwar Talekar wrote:
> > > > Though its some additional work....it will add great value to the
> > > > MSF.
> > > >
> > > > Looking for the dates in next release :)
>
>
>
> --
> With Regards
> Nagareshwar




--
With Regards
Nagareshwar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.metasploit.com/pipermail/framework/attachments/20051003/9b80fbb6/attachment.htm>