Title: Sesame Unauthorized Repository Access Vulnerability
Severity: MODERATE
Description:
Sesame is a web based Resource Description Framework (RDF) repository application that facilitates storage and retrieval of RDF information. It supports a multi-user, multi-repository interface and is implemented in Java. Sesame will run on any Java enabled platform.
It has been reported that the Sesame RDF repository application is prone to an unauthorized repository access vulnerability. This issue is due to a failure of the application to properly secure repository contents in memory once they have been accessed.
The problem presents itself when the application is running under Tomcat Servlet/JSP container while multiple users are accessing their respective repositories. Apparently Tomcat Servlet/JSP container re-uses application threads once they are no longer needed, and so they may be used for repository access by multiple users at different times. Sesame failed to secure the repository information accessed via the offending thread, and so it is possible for an attacker to gain access to an unsuspecting user's repository while the user is currently logged in.
Current information surrounding this issue is limited; this BID will be updated as further details are released.
This issue might allow an attacker to gain access to other users repositories; potentially leading to the disclosure of sensitive information.
Affected Products:
- Sesame RDF container 1.0.0
- Sesame RDF container 1.0.0PRE-1
- Sesame RDF container 1.0.0PRE-2
- Sesame RDF container 1.0.0PRE-3
- Sesame RDF container 1.0.0PRE-4
References:
- Sesame: Product 1.0.1 changelog
- Sesame: Project Home Page
Juniper Networks provides this content via a wide variety of sources and production methods. If notified of errors or omissions in the content of this page, Juniper Networks, at its discretion, will modify or remove the page or leave the content as is, depending on various factors including but not limited to the reputation and authority of the party providing the notification. Please use the contact information displayed elsewhere on this page to report any errors or omissions regarding the content on this page.
