New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

fuboat opened this issue

Apr 12, 2023

· 0 comments

Closed

virtuoso 7.2.9 crashed at __nss_database_lookup #1121

fuboat opened this issue

Apr 12, 2023

· 0 comments

Comments

The PoC is generated by my DBMS fuzzer.

CREATE TABLE t1 (c1 INT, c2 BINARY(100),c3 FLOAT); INSERT INTO t1 VALUES (100,’abcdefghij’,3.0); CREATE TABLE t2 (c1 INT, c2 VARCHAR(100)); INSERT INTO t2 VALUES (2,’abcde’); UPDATE t1 SET c2 = (SELECT MAX(c1) FROM t2);

backtrace:

#0 0x7fd63dbe3a7d (__nss_database_lookup+0x2861d) #1 0xffffffffffffffff – no symbol name found

ways to reproduce (write poc to the file ‘/tmp/test.sql’ first):

remove the old one

docker container rm virtdb_test -f

start virtuoso through docker

docker run --name virtdb_test -itd --env DBA_PASSWORD=dba openlink/virtuoso-opensource-7:7.2.9

wait the server starting

sleep 10

check whether the simple query works

echo “SELECT 1;” | docker exec -i virtdb_test isql 1111 dba

run the poc

docker exec -i virtdb_test isql 1111 dba < “/tmp/test.sql”

1 participant