StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14479046
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-23T11:50:49.973
FavoriteCount
0
LastActivityDate
2013-01-23T11:50:49.973
LastEditDate
LastEditorUserId
0
OwnerUserId
223992
ParentId
14478502
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
There's a number of issues here. Assuming that you have identified SQL injection as a vulnerability (and leaving aside that you also need to establish whether this was the exploited vulnerability in previous attacks, along with investigating and elimintaing any other vulnerabilities - which are very likely to exist) then... I accept that it may not be practical to correct the configuration of a code base which has been built around magic_quotes enabled, but fixing the config first is the correct way to address the problem. Further, one of the problems with magic_quotes is that some extensions enable them via a backdoor route - you can't necessarily rely on get_magic_quotes_gpc(). But if the confiugration is not changing then the behaviour will be consistent - so measure the behaviour and adjust your code accordingly. If magic quotes are enabled, then ideally you should put in place your own indicator of whether magic quotes are currently enabled - which will make life simpler when someone gets round to fixing the problem properly. But the first big WTF here, is why are you using your own code to escape data? The only ways you shoul be doing this are via mysql_real_escape_string() or via bound parameters. There is no way you should be using remove_spc_chr() as a method of escaping data for splicing into SQL strings. The second WTF here is that you seem to be trying to address different types of attack with your rewrite tules - which implies that you don't know what the vulnerabilities are. But your rewrite config only addresses a few, very specific attacks. A better solution would be to use mod_security and/or fail2ban. Using index.html as a generic error handler does not provide a good user experience. <blockquote> I thought there is a problem with server because some port was not secure </blockquote> If that's the case, then nothing you do to the webserver will improve security. <blockquote> I am not able to find and communicate that with server administrator </blockquote> If that's the case, then there's very little you can do to improve security.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP and htaccess security
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsymcbean
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.