S-290: Vulnerability in Microsoft Jet Database Engine (JET)


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-290: Vulnerability in Microsoft Jet Database Engine (JET)
# 1  
Old 05-13-2008
S-290: Vulnerability in Microsoft Jet Database Engine (JET)

A buffer overfun vulnerability exists in the Microsoft Jet Database Engine (JET) that could allow remote code execution on an affected system. An attacker could exploit the vulnerability by creating a specially crafted database query and sending it through an application that is using Jet on an affected system. The risk is MEDIUM. An attacker who successfully exploited this vulnerability could take complete control of an affected system.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Web Development

Oracle JET 4.x - Lesson 1 - Part 9: Oracle JET Cookbook (Gauges and Ints)

Working on: 10. Lesson 1: Oracle JET 4.x - Lesson 1 - Part 9: Oracle JET Cookbook (which I highly recommend) and using the server loadavg code I wrote and have been adding gauges. All is great so far, and I'm loving JET, but have ran into an issue. Here is the loadavg.js code: /** ... (1 Reply)
Discussion started by: Neo
1 Replies

2. Web Development

Oracle Jet - LP: 10. Lesson 1: Oracle JET 4.x - Lesson 1 - Part 4: Data Binding

Working on LP: 10. Lesson 1: Oracle JET 4.x - Lesson 1 - Part 4: Data Binding in this Oracle JET online course - Soar higher with Oracle JavaScript Extension Toolkit (JET), I have created this code for incidents.js I cannot get the load average data in this Oracle JET test to update the... (4 Replies)
Discussion started by: Neo
4 Replies

3. Solaris

JET and non-global Zone

Hi guys, I would like to install a Jet-Server into a non-global zone and i'm running in the nfs problem (there is no nfs-server implementation for non-global zones) has anyone done this already? or have a workaround? thx ---------- Post updated at 05:03 AM ---------- Previous update... (0 Replies)
Discussion started by: beta17
0 Replies
Login or Register to Ask a Question
DtMmdbSectionGetLoc(library call)										 DtMmdbSectionGetLoc(library call)

NAME
DtMmdbSectionGetLoc -- obtains a section's locator SYNOPSIS
#include <DtMmdb.h> const char* DtMmdbSectionGetLoc( DtMmdbInfoRequest* request); DESCRIPTION
The DtMmdbSectionGetLoc function returns the logical identifier for the specified section. Do not use the free function on the returned pointer. No table lookup is involved. The space used by the returned locator pointer is likely to be reused by the database engine when any of the API functions are invoked again. You must make a copy of the content if you want to retain it across multiple API calls. This behavior holds true for all functions that return a const char* pointer. ARGUMENTS
request Specifies the bookcase in the bookcase descriptor field and the section's Database Engine (object) identifier in the primary_oid field. The DtInfo Database Engine identifier is assigned to the section when it is stored. RETURN VALUE
If DtMmdbSectionGetLoc completes successfully, it returns a pointer to a NULL-terminated locator string. If it fails, it returns a NULL pointer. EXAMPLE
The following shows how a DtMmdbSectionGetLoc call might be coded. const char* locator = 0; DtMmdbInfoRequest request; int bd = DtMmdbGetBookCase(myInfoLibPtr, "myBase"); if ( bd >= 0) { request.bookcase_descriptor = bd; request.sequence_num = 1; request.primary_oid = DtMmdbBookGetTocObjectId(&request); locator = DtMmdbSectionGetLoc(&request); } SEE ALSO
TO BE SUPPLIED DtMmdbSectionGetLoc(library call)