svn: /phpdoc/en/trunk/security/ database.xml
| From: | Daniel P. Brown | Date: | Wed, 29 Jun 2011 20:47:40 +0000 |
| Subject: | svn: /phpdoc/en/trunk/security/ database.xml | ||
| Groups: | php.doc.cvs | ||
| Request: | Send a blank email to doc-cvs+get-8342@lists.php.net to get a copy of this message | ||
danbrown Wed, 29 Jun 2011 20:47:40 +0000
Revision: http://svn.php.net/viewvc?view=revision&revision=312637
Log:
Rewrite of the section title (though not the anchor) and the paragraph text.
Changed paths:
U phpdoc/en/trunk/security/database.xml
Modified: phpdoc/en/trunk/security/database.xml
===================================================================
--- phpdoc/en/trunk/security/database.xml 2011-06-29 19:56:30 UTC (rev 312636)
+++ phpdoc/en/trunk/security/database.xml 2011-06-29 20:47:40 UTC (rev 312637)
@@ -347,16 +347,19 @@
</para>
<sect2 xml:id="security.database.avoiding">
- <title>Avoiding techniques</title>
+ <title>Avoidance Techniques</title>
<simpara>
- You may plead that the attacker must possess a piece of information
- about the database schema in most examples. You are right, but you
- never know when and how it can be taken out, and if it happens,
- your database may be exposed. If you are using an open source, or
- publicly available database handling package, which may belong to a
- content management system or forum, the intruders easily produce
- a copy of a piece of your code. It may be also a security risk if it
- is a poorly designed one.
+ While it remains obvious that an attacker must possess at least some
+ knowledge of the database architecture in order to conduct a successful
+ attack, obtaining this information is often very simple. For example,
+ if the database is part of an open source or other publicly-available
+ software package with a default installation, this information is
+ completely open and available. This information may also be divulged
+ by closed-source code - even if it's encoded, obfuscated, or compiled -
+ and even by your very own code through the display of error messages.
+ Other methods include the user of common table and column names. For
+ example, a login form that uses a 'users' table with column names
+ 'id', 'username', and 'password'.
</simpara>
<simpara>
These attacks are mainly based on exploiting the code not being written