Red Hat's directory server
Managing large networks is a challenging task in a number of ways. One of
those challenges is dealing with user information throughout a large
institution. A single system can keep that information in
/etc/passwd, and a small network can rely on tools like
rsync or NIS. When the scale of the network gets large enough,
however, and a sufficient number of levels of politics gets in the way,
simple tools will no longer do the job in an easy or reliable manner. There
comes a point where this information needs to live in a central database
and be made available as needed across the network.
The larger proprietary software vendors - Microsoft, Sun, Novell, etc. -
have long offered directory server products aimed at large network
("enterprise") deployment. These products not only make basic user
information available network-wide; they can also be used to distribute a
wider array of information. Directory servers are a useful and necessary
tool, and the competition in this area is fierce.
Red Hat has set itself up to compete directly with the other "enterprise"
software companies. To that end, Red Hat has put together a number of valuable products and
services, but, so far, it has not been able to offer a directory server as
part of its solution. That gap in Red Hat's offerings has increasingly
looked like a liability, especially as Novell increases its efforts to
compete in the same space. So Red Hat needed a directory server. It found
one, some time ago, when it acquired many of the remaining bits of Netscape
from AOL. Since the acquisition, however, little has been heard about the
former Netscape's offerings.
Until now. On June 1, Red Hat announced
the availability of its directory server product. The (now) Red Hat Directory
Server is fast, with an impressive array of capabilities; for the full
list, see the
product sheet [PDF]. The directory server product is sold like Red Hat
Enterprise Linux: by subscription. Pricing is not yet available.
The Red Hat Directory Server also resembles RHEL in another way: it has a Fedora
equivalent. The Fedora Directory Server Project is where the
development work will be done; the site offers source, documentation,
mailing lists, etc. It is, in other words, just another free software
development project.
At the Fedora site, one can see that, in fact, not all of the directory
server code has been released - yet. The server itself is available under
a special GPL+Exception
license. The code is generally governed by the terms of the GPL, with
the exception that plugin modules can remain proprietary. Those modules,
however, must restrict themselves to a carefully-specified set of
interfaces; anything linking to any other part of the server can only be
distributed under the GPL. Other parts of the system - the management
console and admin server components - remain non-free, though they are
available in binary format. Red Hat plans to free that code as well, but
some work is involved; those components are written in Java, and do not
play well with the free Java implementations.
The Fedora project has some ambitious goals; the best description of what
they have in mind can be found in Christopher
Blizzard's weblog. The project claims to want to bring in outside
developers, and to make them "feel that they are equals." Given all that
the directory server hackers want to do, they will almost certainly need
some help from outside. Consider this:
One of our larger technical objectives - as I've said - is to
integrate with as much software as possible. This means that when
possible we're a configuration store for every application on a
system. Every user pref. Every service on your machine can store
its configuration in one of these servers. Have you ever had the
vision of dropping a machine on a network and having it come up,
self-install, and just start working? We'd like to see it too
because it offers compelling cost of ownership argument that we
think free software is in a unique position to provide. But it
requires participation from the larger software development
community. This means you and your project.
To some readers, this vision sounds like the Windows registry - except that
it's a nightmare, monster central registry for thousands of users. The
"everything lives in the directory server" approach clearly will not be for
everyone. But, for people wanting to create a single, integrated
environment across a large organization, this vision will have some
appeal. It is truly a view of the network as a single, large computer,
with a minimum of boundaries. It promises to reduce the cost of
administering large numbers of systems. One can see why Red Hat thinks it needs to
go in this direction to remain competitive in the future.
High-end directory servers have, so far, been the domain of expensive,
proprietary software. The freeing of the Netscape server, if handled well,
could bring an end to that era. So this move by Red Hat is important, and
deserving of support. High-quality free infrastructure is a good thing.
Comments (24 posted)
A survey of RSS aggregators
Over the years, the proliferation of news sites, weblogs and other sites
with daily updates has made it nearly impossible for the average user to
visit every site of interest in a timely fashion. For those of us who want
or need to keep informed on a variety of topics, RSS, RDF and Atom feeds
have become a nearly indispensable tool to skim the headlines for many
sites at once without having to spend more than an hour per day clicking
through bookmarks. However, this raises the question of how to manage
news feeds effectively.
There are a fair number of RSS aggregator projects on Freshmeat, but we
decided to limit our scope to applications that are fairly mature, have
been updated recently (many RSS aggregator projects listed on Freshmeat
have not been updated in years) and run on the desktop. In particular, we
were looking for aggregators that handle a large number of feeds, make it
easy to manage feeds and integrate well with the Linux desktop and the
average user's workflow.
For some time now, this writer has used the Bloglines service to browse RSS
feeds. For this article, the feed list from Bloglines, containing about 130
RSS/RDF and Atom feeds, was exported as an OPML file and imported that
into each of the aggregators to see how they performed.
RSSOwl
The first aggregator we'll look at is RSSOwl. This aggregator is written in
Java, using the SWT graphic library. RSSOwl has a fairly flexible
interface, and opens up tabs for each new feed that the user opens from the
list of "favorites."
There are a few interesting features in RSSOwl. First, RSSOwl has an export
feature, which can be used to export a feed or individual article to PDF,
Rich Text (RTF) or HTML. This might be handy for saving feeds and entries
for later. RSSOwl also supports AmphetaRate, a
centralized ratings service for rating articles found in news feeds.
Oddly, it seems to display feeds as plain text rather than rendering the
HTML. We're not sure if this is a glitch in RSSOwl or if we missed a step
in setting it up. Otherwise, RSSOwl's performance was very good, and it
handled a large number of feeds without any problems.
Snownews
The Snownews
aggregator is unique in this list, because it's not a graphical
application. Snownews is a console-based feed-reader that uses ncurses, and
is a fairly straightforward application with few frills.
Snownews does not support OPML directly, but there is an "opml2snow" script
that comes with Snownews to convert OPML into the format that Snownews
likes. It's a little more of a hassle than the easy-import offered by other
readers, but it gets the job done. Snownews displays headlines and feeds
inline. To follow the feed URL, one must use an external browser. It works
fairly well with GUI browsers, but works best (at least in this writer's
opinion) with a text-mode browser like w3m or Lynx.
It's probably not going to be the first choice for most users, but those
who prefer browsing in w3m or other text-mode browsers should definitely
check it out.
Liferea
One reader that seems to be getting a lot of attention at the moment is the
Linux Feed Reader, Liferea. This is a
nicely-designed newsreader that's easy to use. It imported our OPML file
with no problems, and gives the user the option of rendering HTML with
Mozilla or GtkHTML2. It spawns an external browser for full articles rather
than displaying them within the Liferea window. This works well if you
prefer to browse content in Firefox, Epiphany or another browser, but we
would like it if Liferea would give the option of displaying the entire
article inside Liferea itself.
One interesting feature with Liferea is the ability to create a new feed
from a Feedster search. This can be
quite handy if you're interested in finding feeds on a specific topic from
a variety of sources.
If one wishes to be alerted, or interrupted, with updates from subscribed
feeds, Liferea has a feature that will pop up a notification window at
regular intervals with new headlines. We enabled this feature briefly, but
turned it off after an hour or so, finding it quite distracting.
We also found Liferea to be a bit less than stable, at least the 0.9.0
release that is available in Ubuntu Hoary. Liferea crashed a few times when
doing something as simple as deleting a feed. Overall, its performance was
quite good, and the interface is excellent -- but it might need to
stabilize a bit before being our first choice of the available aggregators.
Blam
Blam is a aggregator
written in C# using Mono and GTK#. It's a little more basic than Liferea or
Snownews, but it serves well as a basic newsreader. Headlines and summaries
are displayed within Blam, but it requires an internal browser to follow
links.
At first, Blam would not import the OPML from Bloglines. We tried
subscribing a few feeds manually and then exporting Blam's list to OPML to
find out what was different. The difference was that Bloglines uses "title"
for the name of each feed, and Blam expects "text" -- after doing a quick
search and replace in Vim, changing "title" to "text," Blam imported the
list of feeds just fine.
Blam is a good choice for users who want a very basic newsreader that's
fast and light.
Akregator
KDE users are probably already familiar with Akregator. This reader uses
KHTML to display full articles in tabs within the Akregator interface, at
least by default. Akregator can also be configured to use an external
browser for those who prefer Firefox or another browser to
Konqueror/KHTML.
For users who prefer Konqueror for Web browsing, Akregator is an excellent
choice. Konqueror auto-discovers feeds on pages, and makes it easy to add
those feed subscriptions to Akregator. Akregator has fewer frills than
Liferea or RSSOwl, but it integrates very well with KDE and performs well.
Firefox and Thunderbird
We should also mention Firefox and Thunderbird. While not dedicated
aggregators, both applications allow users to read and manage
news feeds. However, they lack a number of features that many users would
want, at least natively. The advantage of using Firefox as an aggregator is
that Firefox makes it very easy to create a "Live Bookmark" to subscribe to
feeds, when the browser discovers the feed in a page.
If Firefox doesn't detect the feed, that complicates things
greatly. Firefox supports adding a bookmark manually, but does not support
adding a feed manually. The Live Bookmark also doesn't allow the user to
preview the content or full text, just the headlines from a feed. Firefox
doesn't support importing OPML files natively, so users with large
subscription lists would have to go through a lot of work to re-subscribe
to sites using Firefox.
Of course, it is possible to extend Firefox's capabilities with
extensions. We tried the Sage
extension with Firefox, and were quite pleased with it. The Sage extension
adds a sidebar to Firefox much like the Bookmarks and History
sidebars. There are two panes in the sidebar, a list of subscriptions and
lower pane that lists headlines from the selected feed.
The integration with Firefox makes it a convenient aggregator for those of
us who use Firefox exclusively or extensively. Sage had no problem
importing the OPML list exported from Bloglines, and its performance was
quite acceptable. There are a number of other news
reading extensions for Firefox for those who are interested.
Thunderbird, by itself, is also limited in its abilities to import and
manage feeds. For users who spend a lot of time in their e-mail client, and
who have a fairly limited number of feeds, it would work well -- but this
writer would not like to have to import 100 or more feeds using the "Manage
Subscription" dialog for Thunderbird. The advantage to using Thunderbird
for feeds is the ability to mail links from subscribed feeds.
We found the Forumzilla extension
for Thunderbird, which adds OPML import and other features to
Thunderbird. Unfortunately, it consistently crashed Thunderbird when trying
to import the OPML exported from Bloglines.
Summary
After spending time with each of these aggregators, this writer prefers
Liferea and Sage, though any of the aggregators would do in a pinch. Given
the variety and maturity of the various options, Linux users should not
have much trouble finding an aggregator that works well for them.
Comments (11 posted)
IP Software Compliance Tools -- Who Needs Them and Why?
June 1, 2005
By Pamela Jones, Editor of Groklaw
When
Black Duck Software
first made available its software compliance tool, ProtextIP, about a
year ago, the typical first reaction was to view it as a response to
SCO's lawsuit.
Now there is a second such product, Palamida's IP Amplifier, and it's
clear there is a market for such products. Cisco, for one, has just signed
on with Palamida. Who really needs products like this, and why? And is
there a difference between them?
Who Needs Software Compliance Tools?
Now that Free and Open Source software has hit the mainstream of the
enterprise, businesses need to be certain that they are not taking on
legal liabilities with the code. There are many licenses, and making
sure a company is abiding by them all is complex. That's one reason you
are hearing so many voices calling for simplifying and settling on fewer
licenses. But it goes deeper than that.
"Everyone who distributes software should know what goes into it," attorney
Lawrence Rosen explains. "And almost everyone who distributes software
wants to comply with the relevant licenses. Most reputable software-based
businesses recognize that playing fast-and-loose with copyright claims
isn't worthwhile."
While most businesses today are pleased to adopt and incorporate open
source products into their products and services, they want to know what
licenses apply so that they can comply with the terms.
"That's what Black Duck and Palamida make possible," Rosen adds. "A
distributor or user can know what open source software is in its own
software and act accordingly, early in the cycle. It's now possible to
evaluate license compatibility for specific component sets and plan
appropriate combinations for use in products to be developed."
Unfortunately, developers sometimes use GPL code (or other licensed FOSS
code) without telling management, thinking it's public domain. It
isn't. And with outsourcing, sometimes developers are in other countries
that may have more relaxed views on copyright and this can cause problems.
So when developers let things happen they shouldn't (such as making
unauthorized
copies or derivative works), companies have an automated way to catch
some of that and react appropriately before much bigger problems can
develop.
Software practices are also changing. Application development today is
becoming more like an assembly line, more a matter of assembling bits
of code from open source projects and from outsourced firms and
incorporating them into proprietary products than handcrafting 100%
custom software. This isn't a bad thing, because it makes it possible to
avoid having to reinvent the wheel -- one of the advantages of Open Source
-- but it also means that checking on license terms and making sure you
are complying with them all is vital to the process.
And there is no doubt that enforcement of GPL violations is increasing,
as Fortinet learned recently when a German court banned their
U.K. subsidiary from further distribution of their firewall and antivirus
products until they complied with the GPL, which they promptly did.
Then there is the Sarbanes-Oxley Act [PDF], and its
requirements for IT audits.
"The SEC’s new rules on heightened corporate responsibility for public
company reporting known as Sarbanes-Oxley require public companies to
abide by internal procedures that are sufficient to provide reasonable
assurance that the financial and non-financial information required to be
disclosed in its periodic and current reports is accurate," says Karen
Copenhaver, executive vice president and general counsel for Black Duck
Software.
"Specifically, Sarbanes creates two new corporate governance requirements:
assessment of internal controls over financial reporting (required by
section 404 of the Act), and heightened corporate responsibility for
financial reports (required by section 302 of the Act). It would be hard
to overestimate the burden that compliance with these new rules has placed
on public companies in the first few years since their enactment.
"Even before Sarbanes, public companies were required to address
intellectual property matters in their current and periodic reports. A
reporting company traditionally discloses the importance of its
intellectual property assets to the company’s business and any third-party
intellectual property encumbrances on the company’s ability to conduct its
business. To the extent that a failure to identify or comply with third
party license obligations has an effect on the accuracy of any of this
information, public companies will be concerned about compliance with
their obligations under Sarbanes."
Obviously, Sarbanes-Oxley has upped the ante considerably. But most
businesses and developers want to do the right thing anyway, apart from
outside pressures. The tools don't set policy for a company, but they
surely make it easier to make sure policies are observed.
What Do the Tools Offer?
Before automated software compliance tools were available, due diligence
in checking software for infringing code was done by assigning the tedious
task to senior software programmers in the company, who, together with
lawyers laboriously looked through the code. The problem with such a
system, aside from the time it required and the drudgery, is that no one
person knows all the Free and Open Source projects available by sight, let
alone all the proprietary products you are not allowed to see without
complex legal arrangements.
Automated systems are an obvious answer. What they provide is a
Google-like collection of code. They've collected it all for you. Both
tools scan for copyright infringement and can spot more than verbatim
matches. But they do more than scan.
Palamida says its IP Amplifier product automatically detects, manages and
reports on the third party, commercial and open source components that may
exist in their software code base. It consists of two key modules -- the
Compliance Library and the Detector. Using an automated collection system,
the Compliance Library contains billions of source code snippets and
millions of files of the most commonly used open source projects found in
the market.
Palamida: "The Palamida IP Amplifier uses three different types of
technologies to automate detection, source code fingerprinting, file
digest matching, and for Java files, namespace matching. This means the
software is able to conduct both source code and binary code analysis. So
for companies whose developers download whole libraries, compiled code,
XML files, icons, text files, and include those resources into their code
base, the software will still detect their usage even though their source
code is not available and even if we do not have the components listed in
our database."
Next, there is a "layer of analysis that is beyond just code matching for
reduction of false positives. We call this technology CodeRank™.
CodeRank™ looks at the code matches and evaluates the results on
multiple levels, including uniqueness, coverage and clustering. How unique
is that match to what is in the Palamida database? How much of a customer
file matches a file in Palamida’s database? How dense are the matches –
do they look like a continuous cut and paste or does it look like two
engineers coded against the same API?"
After their software evaluates the code matches, Palamida assigns a
CodeRank number to the matches; the higher the CodeRank number the higher
the chances of copying. In the scan results, users will see a list of all
code that has matches and a list of all the third party products that they
most likely came from, with the most likely on top.
Reports identify all components that include open source and list their
licenses, text and license information, in addition to the CodeRank. All
the information and data is exportable in XML data format, allowing users
to create custom reports, as well as via HTML reports.
Black Duck too offers a great deal more than just code scanning. Black
Duck's Copenhaver: "We do more than just scan code. Our product provides
a full suite of services covering project planning, code analysis and
detection, license analysis and management, auditing and archival
capabilities for the complete life cycle of software projects.
"From an open source perspective," Coperhaver adds, "we help developers
manage the origins and obligations of code that they use so they can meet
the expectations of the industry and community. But everything we do works
for both open source and proprietary or commercial code. Users can add
code prints and licenses into the system to manage their internal
proprietary code along with open source.
"Our product helps people manage the introduction of licensed materials
into their code bases, understand the obligations associated with that
code (and combinations of components from different sources), provide an
environment for controlled remediation of issues that arise and create an
archivable record of the actions that were taken by the team along the
way. Our products are designed to bring together developers, lawyers and
business decision makers into a collaborative environment."
Black Duck offers an analysis 'engine' that processes licenses at a
detailed level and alerts users to license conflicts and obligations of
both software source and binary components and their combinations. The
ProtexIP Knowledgebase contains detailed breakdowns of 500+ software
licenses for automated comparison of license terms and notification of
collective obligations, and the data is remotely updated frequently with
new licenses as they come to market. It recently added what they call
Custom Code Prints, which gives ProtextIP support for proprietary source
code.
Palmida claims a database of 40,000 of the most commonly used OSS projects
and their associated licenses, monitoring more than 38 million open
source files and billions of source code snippets. The Knowledge Base also
contains all pertinent information regarding the open source projects:
name, version number, project name, licensor, licensor information (when
available), license, license text, and project URL, all using an
automated collection toolset that incorporates information on all the new
projects released on the major OSS repositories for real time updates.
The Palamida database takes up less than 10 Gb disk space, thanks to a
compression algorithm, and it's all kept on a customer's own servers,
behind their firewall. Its code is written in Java. IP Amplifier
can be configured to search daily or weekly and has a set of configuration
tools to integrate it into build systems.
Are There Any Differences?
The biggest differentiator is cost. IP Amplifier 3.0 is licensed on an
annual subscription basis, for unlimited number of users, at prices that
begin at $50,000 and go up to $250,000 per year, depending on the
customer's development environment. There is a 30-day Free Trial offer.
Black Duck now offers two options. You can pay an annual licensing fee for
its multiuser ProtextIP product, at $25,000 per year, and then add
additional charges based on the amount of code you have. Or, you can use
their new hosted ProtextIP/OnDemand product, an online system for a
single user, single project, 90-day sessions, for which you pay based on
the amount of code you wish to scan. It costs $3,000 for 10 MB of code and
costs scale up to $25,000 for 100 MBs. A company thinking of acquiring
another might wish to use the online tool, rather than purchase more
costly version.
Both products still require human analysis, naturally. There can be false
matches, if two independent developers happen to write software that is
very much the same, even if there has been no copying, just because there
are only so many ways of writing the same instruction. Both tools
provide not only identical matches but also flag similarities in your
source code to others' programs that are worth your further investigation
and list issues for review. It's important to realize, however, that
the tools scan and analyze copyright issues and licensing issues, not
patent infringement. That is an entirely separate ballgame.
But for what they are designed to do, unquestionably they have
simplified, organized, and improved the due diligence process.
Comments (10 posted)
Page editor: Jonathan Corbet
Security
A Look at The Onion Router (Tor)
Last week we promised a look
at Tor, a system for anonymous Internet
communication, primarily developed by Nick Mathewson and Roger Dingledine. Current
development is supported by the Electronic
Frontier Foundation (EFF), but Tor was originally developed as part of
the U.S. Naval Research Laboratory's Onion Routing program.
As the Tor web page explains, Tor is a "toolset for a wide range of
organizations and people that want to improve their safety and security on
the Internet." What does that mean? In a nutshell, Tor is a
client/server application that anonymizes traffic by routing it from the
client through a series of nodes to hide the origin of a request. It can
also be used to protect services against denial of service attacks and the like by hiding
their origin.
Tor routes traffic through nodes that "know" about the previous node and
the next node -- but not the rest of the network. By routing traffic through a series of
"onion routers" Tor makes it difficult for the receiver, observers and
even other Tor routers to detect the source of traffic. A more complete
description of Tor's design can be found in the design
paper; a protocol
specification is also available for those who wish to build compatible
software.
Tor works as both a server and as a client. By default, Tor runs as a
client only, but it can be configured to allow other users to connect to
your system as a Tor node. In addition, Tor can be used to run "hidden"
services that do not reveal your IP address to others at all. The "hidden
wiki" maintains a list of hidden services that users can see as an
example. Finally, it's possible to set up one's own Tor network that does
not interact with the public Tor network, for those who want to test the
protocol but may lack access to the Internet.
To achieve best results, one may need to use Tor in conjunction with other
applications. For example, users who wish to browse anonymously would use
Tor in conjunction with Privoxy. Other applications may require
use of tsocks or ProxyChains.
To see what Tor had to offer, we installed it on a Ubuntu Hoary machine,
along with Privoxy, tsocks and ProxyChains. Configuring services to work
with Tor is not terribly difficult, and there is a relatively detailed HOWTO
for users who wish to configure specific applications like Gaim, X-Chat,
SSH or BitTorrent with Tor.
It should be noted that using Tor can have an impact on performance for
client applications. Using Tor and Privoxy together for browsing, for
example, introduced a notable lag. Firefox users may be
interested in using the SwitchProxy
Tool extension to switch Proxy use on and off, reserving Tor for
specific sites rather than for all web browsing. Users should also be
prepared for some odd behavior on some sites -- for example, we kept being
redirected to country-specific versions of Google, rather than Google's main
site, when using Tor and Privoxy. Tor itself didn't seem to have much of an
impact on system performance overall.
Tor is not completely foolproof. It could be possible for someone who's
running a Tor server to modify Tor or use other software to monitor traffic
going through the server. Traffic coming out of the "exit node" (the last
hop in the Tor "circuit") is not encrypted, so a malicious user could set
up a Tor server and browse traffic coming out of their machine. (It is
possible to specify your exit node in the Tor configuration.) There are
also potential JavaScript issues, and there are other ways to analyze
traffic that passes through Tor.
Interested users should also have a look at the EFF's legal issues page
about Tor. Though Tor can be used for things like BitTorrent, it is not
designed to assist copyright infringement or other illegal activity.
There is still a lot of development ahead for Tor, but it is definitely
worth a look for users who are interested in anonymous communication on the
Internet. Users with bandwidth to spare are also encouraged to set up and
run a Tor server to help test its scalability and to help provide a larger
Tor network. See the download
page for Tor packages and source code.
Comments (9 posted)
New vulnerabilities
apache-utils: htpasswd buffer overflow
| Package(s): | apache-utils |
CVE #(s): | |
| Created: | May 26, 2005 |
Updated: | June 1, 2005 |
| Description: |
The htpasswd utility has a buffer overflow vulnerability.
Web sites that use an unchecked public interface to htpasswd
can be used to execute arbitrary code with the privileges of
the user who runs htpasswd. |
| Alerts: |
|
Comments (none posted)
gxine: format string vulnerability
| Package(s): | gxine |
CVE #(s): | CAN-2005-1692
|
| Created: | May 26, 2005 |
Updated: | July 23, 2005 |
| Description: |
The gxine media player has a format string vulnerability in the
hostname decoding function. A specially crafted file can be used
to cause a user to execute arbitrary code. |
| Alerts: |
|
Comments (none posted)
ImageMagick: xwd coder denial of service
| Package(s): | ImageMagick |
CVE #(s): | CAN-2005-1739
|
| Created: | May 26, 2005 |
Updated: | July 19, 2005 |
| Description: |
The xwd coder in ImageMagick has a vulnerability that
can be accessed by working on a maliciously created image.
A denial of service can result. |
| Alerts: |
|
Comments (none posted)
Mailutils: multiple vulnerabilities in imap4d and mail
| Package(s): | mailutils |
CVE #(s): | CAN-2005-1520
CAN-2005-1521
CAN-2005-1522
CAN-2005-1523
|
| Created: | May 27, 2005 |
Updated: | June 3, 2005 |
| Description: |
infamous41d discovered several vulnerabilities in GNU Mailutils. imap4d
does not correctly implement formatted printing of command tags
(CAN-2005-1523), fails to validate the range sequence of the "FETCH"
command (CAN-2005-1522), and contains an integer overflow in the
"fetch_io" routine (CAN-2005-1521). mail contains a buffer overflow in
"header_get_field_name()" (CAN-2005-1520). |
| Alerts: |
|
Comments (none posted)
Updated vulnerabilities
a2ps: input validation error
| Package(s): | a2ps |
CVE #(s): | CAN-2004-1170
CAN-2004-1377
|
| Created: | November 26, 2004 |
Updated: | December 19, 2005 |
| Description: |
The GNU a2ps utility fails to properly sanitize filenames, which can be
abused by a malicious user to execute arbitrary commands with the
privileges of the user running the vulnerable application. More
information at Security
Focus. |
| Alerts: |
|
Comments (none posted)
bzip2: race condition and infinite loop
| Package(s): | bzip2 |
CVE #(s): | CAN-2005-0953
CAN-2005-1260
|
| Created: | May 17, 2005 |
Updated: | January 10, 2007 |
| Description: |
A race condition in bzip2 1.0.2 and earlier allows local users to modify
permissions of arbitrary files via a hard link attack on a file while it is
being decompressed, whose permissions are changed by bzip2 after the
decompression is complete. Also specially crafted bzip2 archives may cause
an infinite loop in the decompressor. |
| Alerts: |
|
Comments (2 posted)
cdrdao: local root vulnerability
| Package(s): | cdrdao |
CVE #(s): | CAN-2002-0137
CAN-2002-0138
|
| Created: | May 19, 2005 |
Updated: | May 25, 2005 |
| Description: |
The cdrdao CD burning utility has two vulnerabilities.
Local users can use the show-data command to read arbitrary files,
and local users can overwrite arbitrary files via a symlink attack on
the ~/.cdrdao config file. This can be exploited to gain root
privileges. |
| Alerts: |
|
Comments (none posted)
cheetah: untrusted module search path
| Package(s): | cheetah |
CVE #(s): | |
| Created: | May 19, 2005 |
Updated: | May 25, 2005 |
| Description: |
Cheetah, a Python template engine and code generator,
has a vulnerability in the module importing code that can
be used by a local user to gain escalated privileges. |
| Alerts: |
|
Comments (none posted)
cpio - file permissions error
| Package(s): | cpio |
CVE #(s): | CAN-1999-1572
|
| Created: | February 2, 2005 |
Updated: | July 19, 2005 |
| Description: |
Some versions of cpio contain an ancient vulnerability where files created by that utility have overly generous access permissions. |
| Alerts: |
|
Comments (none posted)
cURL: buffer overflow
| Package(s): | curl |
CVE #(s): | CAN-2005-0490
|
| Created: | February 28, 2005 |
Updated: | July 19, 2005 |
| Description: |
Multiple stack-based buffer overflows in libcURL and cURL 7.12.1, and
possibly other versions, allow remote malicious web servers to execute
arbitrary code via base64 encoded replies that exceed the intended buffer
lengths when decoded. |
| Alerts: |
|
Comments (none posted)
cvs: multiple vulnerabilities
| Package(s): | cvs |
CVE #(s): | CAN-2005-0753
|
| Created: | April 18, 2005 |
Updated: | July 13, 2005 |
| Description: |
CVS (in version prior to 1.11.20) has one or more buffer overflow vulnerabilities, memory leaks, and a NULL pointer dereferencing error.
These can be used to launch a remote denial of service or to remotely
execute arbitrary code. |
| Alerts: |
|
Comments (none posted)
cyrus-imapd: buffer overflows
| Package(s): | cyrus-imapd |
CVE #(s): | CAN-2005-0546
|
| Created: | February 23, 2005 |
Updated: | April 9, 2006 |
| Description: |
Cyrus-imapd, prior to version 2.2.12, contains several buffer overflows which could be exploited by an (authenticated) attacker to run code on the server system. |
| Alerts: |
|
Comments (none posted)
dhcp: format string vulnerability
| Package(s): | dhcp |
CVE #(s): | CAN-2004-1006
|
| Created: | November 4, 2004 |
Updated: | July 13, 2005 |
| Description: |
Dhcp has a format string vulnerability in the log functions of dhcp 2.x
that may be exploited via a malicious DNS server. |
| Alerts: |
|
Comments (none posted)
Dnsmasq: poisoning and DoS
| Package(s): | dnsmasq |
CVE #(s): | |
| Created: | April 4, 2005 |
Updated: | July 21, 2005 |
| Description: |
Dnsmasq does not properly detect that DNS replies received do not
correspond to any DNS query that was sent. Rob Holland of the Gentoo Linux
Security Audit team also discovered two off-by-one buffer overflows that
could crash DHCP lease files parsing. |
| Alerts: |
|
Comments (none posted)
emacs21: format string vulnerability in "movemail"
| Package(s): | emacs21 |
CVE #(s): | CAN-2005-0100
|
| Created: | February 7, 2005 |
Updated: | May 15, 2006 |
| Description: |
Max Vozeler discovered a format string vulnerability in the "movemail"
utility of Emacs. By sending specially crafted packets, a malicious
POP3 server could cause a buffer overflow, which could be exploited to
execute arbitrary code with the privileges of the user and the "mail"
group. |
| Alerts: |
|
Comments (none posted)
enscript: arbitrary code execution
| Package(s): | enscript |
CVE #(s): | CAN-2004-1184
CAN-2004-1185
CAN-2004-1186
|
| Created: | January 21, 2005 |
Updated: | May 27, 2006 |
| Description: |
Erik Sjölund has discovered several security relevant problems in enscript,
a program to convert ASCII text into Postscript and other formats.
Unsanitized input can cause the execution of arbitrary commands via EPSF
pipe support. Due to missing sanitizing of filenames it is possible that a
specially crafted filename can cause arbitrary commands to be executed.
Multiple buffer overflows can cause the program to crash. |
| Alerts: |
|
Comments (none posted)
Ethereal: numerous vulnerabilities
Comments (none posted)
evolution: message crash vulnerability
| Package(s): | evolution |
CVE #(s): | CAN-2005-0806
|
| Created: | March 17, 2005 |
Updated: | August 11, 2005 |
| Description: |
The Evolution mail client can be crashed when reading
certain types of messages. |
| Alerts: |
|
Comments (none posted)
firefox: multiple vulnerabilities
Comments (2 posted)
Foomatic: Arbitrary command execution in foomatic-rip
| Package(s): | foomatic |
CVE #(s): | CAN-2004-0801
|
| Created: | September 20, 2004 |
Updated: | May 31, 2006 |
| Description: |
There is a vulnerability in the foomatic-filters package. This
vulnerability is due to insufficient checking of command-line parameters
and environment variables in the foomatic-rip filter. This vulnerability
may allow both local and remote attackers to execute arbitrary commands on
the print server with the permissions of the spooler. |
| Alerts: |
|
Comments (none posted)
FreeRADIUS: buffer overflow and SQL injection
| Package(s): | freeradius |
CVE #(s): | CAN-2005-1454
CAN-2005-1455
|
| Created: | May 17, 2005 |
Updated: | June 23, 2005 |
| Description: |
Primoz Bratanic discovered that the sql_escape_func function of FreeRADIUS
1.0.2 and earlier may be vulnerable to a buffer overflow. He also
discovered that FreeRADIUS fails to sanitize user-input before using it in
a SQL query, possibly allowing SQL command injection. |
| Alerts: |
|
Comments (1 posted)
gdb: multiple vulnerabilities
| Package(s): | gdb |
CVE #(s): | CAN-2005-1704
CAN-2005-1705
|
| Created: | May 20, 2005 |
Updated: | August 11, 2006 |
| Description: |
Tavis Ormandy of the Gentoo Linux Security Audit Team discovered an integer
overflow in the BFD library, resulting in a heap overflow. A review also
showed that by default, gdb insecurely sources initialization files from
the working directory. Successful exploitation would result in the
execution of arbitrary code on loading a specially crafted object file or
the execution of arbitrary commands. |
| Alerts: |
|
Comments (5 posted)
gtk-pixbuf, gtk2: denial of service
| Package(s): | gdk-pixbuf gtk2 |
CVE #(s): | CAN-2005-0891
|
| Created: | March 30, 2005 |
Updated: | December 19, 2005 |
| Description: |
The BMP image processing code in gdk-pixbuf and gtk2 contains a denial of service vulnerability exploitable via a specially crafted image file.
|
| Alerts: |
|
Comments (none posted)
gettext: Insecure temporary file handling
| Package(s): | gettext |
CVE #(s): | CAN-2004-0966
|
| Created: | October 11, 2004 |
Updated: | March 1, 2006 |
| Description: |
gettext insecurely creates temporary files in world-writeable directories
with predictable names. A local attacker could create symbolic links in
the temporary files directory, pointing to a valid file somewhere on the
filesystem. When gettext is called, this would result in file access with
the rights of the user running the utility, which could be the root user. |
| Alerts: |
|
Comments (1 posted)
gftp: missing input sanitizing
| Package(s): | gftp |
CVE #(s): | CAN-2005-0372
CAN-2004-1376
|
| Created: | February 17, 2005 |
Updated: | July 13, 2005 |
| Description: |
gftp has a directory traversal vulnerability.
A remote server could use specially crafted filenames to overwrite
local files.
|
| Alerts: |
|
Comments (none posted)
ghostscript: symlink vulnerabilities
| Package(s): | ghostscript |
CVE #(s): | CAN-2004-0967
|
| Created: | October 20, 2004 |
Updated: | September 28, 2005 |
| Description: |
The ghostscript package (prior to version 7.07.1-r7) contains several scripts which are vulnerable to symlink attacks. |
| Alerts: |
|
Comments (none posted)
glibc: Information leak with LD_DEBUG
| Package(s): | glibc |
CVE #(s): | CAN-2004-1453
|
| Created: | August 17, 2004 |
Updated: | May 26, 2005 |
| Description: |
Silvio Cesare discovered a potential information leak in glibc. It allows
LD_DEBUG on SUID binaries where it should not be allowed. This has various
security implications, which may be used to gain confidential information.
An attacker can gain the list of symbols a SUID application uses and their
locations and can then use a trojaned library taking precedence over those
symbols to gain information or perform further exploitation. |
| Alerts: |
|
Comments (1 posted)
glibc: tempfile vulnerability in catchsegv script
| Package(s): | glibc |
CVE #(s): | CAN-2004-0968
|
| Created: | October 21, 2004 |
Updated: | November 14, 2005 |
| Description: |
The catchsegv script in the glibc package has a symlink vulnerability
that may allow a local user to overwrite arbitrary
files with the permissions of the user that is running the script. |
| Alerts: |
|
Comments (none posted)
gnupg: information leak
| Package(s): | gnupg |
CVE #(s): | CAN-2005-0366
|
| Created: | March 16, 2005 |
Updated: | August 19, 2005 |
| Description: |
GnuPG (and other PGP-like systems) suffers from an information leak which could, in some situations, be used by an attacker to obtain plain text from an encrypted message. See this message for a detailed explanation of the problem. "We know of no real-world application that is affected by this type of attack. It is an attack that requires the active participation of someone who holds the actual key required to decrypt a message. Thus, it is not something you are likely to see." |
| Alerts: |
|
Comments (none posted)
GnuTLS: Denial of Service vulnerability
| Package(s): | gnutls |
CVE #(s): | CAN-2005-1431
|
| Created: | May 9, 2005 |
Updated: | June 1, 2005 |
| Description: |
GnuTLS 1.2.3 and 1.0.25 have been
released, fixing a denial of service problem. |
| Alerts: |
|
Comments (none posted)
grip: buffer overflow
| Package(s): | grip |
CVE #(s): | CAN-2005-0706
|
| Created: | March 10, 2005 |
Updated: | September 16, 2005 |
| Description: |
Grip, a CD ripper, has a buffer overflow vulnerability that can
occur when the CDDB server returns more than 16 matches. |
| Alerts: |
|
Comments (none posted)
groff: insecure temporary directory
| Package(s): | groff |
CVE #(s): | CAN-2004-0969
|
| Created: | November 1, 2004 |
Updated: | February 9, 2006 |
| Description: |
Recently, Trustix Secure Linux discovered a vulnerability in the groff
package. The utility "groffer" created a temporary directory in an
insecure way, which allowed exploitation of a race condition to create
or overwrite files with the privileges of the user invoking the
program. |
| Alerts: |
|
Comments (none posted)
gzip: race condition and directory traversal
| Package(s): | gzip |
CVE #(s): | CAN-2005-0988
CAN-2005-1228
|
| Created: | May 4, 2005 |
Updated: | July 13, 2005 |
| Description: |
gzip suffers from a race condition which could allow a fast-fingered attacker to change the permissions on files owned by others. There is also a directory traversal vulnerability associated with the -N option.
|
| Alerts: |
|
Comments (none posted)
htdig: cross site scripting
| Package(s): | htdig |
CVE #(s): | CAN-2005-0085
|
| Created: | February 14, 2005 |
Updated: | January 10, 2006 |
| Description: |
Michael Krax discovered that ht://Dig fails to validate the 'config'
parameter before displaying an error message containing the parameter.
This flaw could allow an attacker to conduct cross-site scripting
attacks. |
| Alerts: |
|
Comments (none posted)
ImageMagick: heap corruption
| Package(s): | ImageMagick |
CVE #(s): | CAN-2005-1275
|
| Created: | April 28, 2005 |
Updated: | May 25, 2005 |
| Description: |
ImageMagick 6.2.1 and earlier has a heap corruption problem
in the pnm coder. |
| Alerts: |
|
Comments (1 posted)
imap: buffer overflow in c-client
| Package(s): | imap |
CVE #(s): | CAN-2003-0297
|
| Created: | February 18, 2005 |
Updated: | April 9, 2006 |
| Description: |
A buffer overflow flaw was found in the c-client IMAP client. An attacker
could create a malicious IMAP server that if connected to by a victim could
execute arbitrary code on the client machine. |
| Alerts: |
|
Comments (none posted)
imlib2: buffer overflows
| Package(s): | imlib2 |
CVE #(s): | CAN-2004-0802
CAN-2004-0817
|
| Created: | September 8, 2004 |
Updated: | October 26, 2005 |
| Description: |
The imlib2 library contains buffer overflows in the BMP handling code. |
| Alerts: |
|
Comments (none posted)
infozip: privilege escalation, directory-traversal
| Package(s): | infozip |
CVE #(s): | CAN-2003-0282
CAN-2004-1010
CAN-2005-0602
|
| Created: | May 2, 2005 |
Updated: | August 1, 2005 |
| Description: |
InfoZip reports that Zip 2.3 and
(presumably) all previous versions have a buffer-overrun vulnerability
relating to deep directory paths that could potentially lead to local
privilege escalation (e.g., in the case of automated, Zip-based backups).
All versions of UnZip through 5.50 have a number of directory-traversal
vulnerabilities. |
| Alerts: |
|
Comments (1 posted)
junkbuster: heap corruption and settings modification
| Package(s): | junkbuster |
CVE #(s): | CVE-2005-1108
CVE-2005-1109
|
| Created: | April 13, 2005 |
Updated: | November 5, 2005 |
| Description: |
JunkBuster through version 2.02-r2 contains two vulnerabilities: a heap corruption bug and a possible privacy violation. |
| Alerts: |
|
Comments (1 posted)
kdelibs: unsanitzied input
| Package(s): | kdelibs |
CVE #(s): | CAN-2004-1165
|
| Created: | January 10, 2005 |
Updated: | July 19, 2005 |
| Description: |
Thiago Macieira discovered a vulnerability in the kioslave library,
which is part of kdelibs, which allows a remote attacker to execute
arbitrary FTP commands via an ftp:// URL that contains an URL-encoded
newline before the FTP command. |
| Alerts: |
|
Comments (none posted)
kernel: multiple vulnerabilities
| Package(s): | kernel |
CVE #(s): | CAN-2005-0400
CAN-2005-0749
CAN-2005-0750
CAN-2005-0815
CAN-2005-0839
|
| Created: | April 1, 2005 |
Updated: | July 1, 2005 |
| Description: |
More kernel vulnerabilities have been discovered including:
- Mathieu Lafon discovered
an information leak in the ext2 file system driver. (CAN-2005-0400)
- Yichen Xie discovered a Denial of Service vulnerability in the ELF
loader. (CAN-2005-0749)
- Ilja van Sprundel discovered that the bluez_sock_create() function
did not check its "protocol" argument for negative values.
(CAN-2005-0750)
- Michal Zalewski discovered that the iso9660 file system driver fails
to check ranges properly in several cases. (CAN-2005-0815)
- Previous kernels did not restrict the use of the N_MOUSE line
discipline in the serial driver. (CAN-2005-0839)
|
| Alerts: |
|