+- Sinisterly (https://sinister.ly)
+-- Forum: Coding (https://sinister.ly/Forum-Coding)
+--- Forum: PHP (https://sinister.ly/Forum-PHP)
+--- Thread: [*FIXED*] Issue with in_array() [strange] (/Thread-FIXED-Issue-with-in-array-strange)
RE: Issue with in_array() [strange] - hellomen - 10-29-2013
(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
RE: Issue with in_array() [strange] - hellomen - 10-29-2013
(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
RE: Issue with in_array() [strange] - hellomen - 10-29-2013
(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
RE: Issue with in_array() [strange] - hellomen - 10-29-2013
(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
RE: Issue with in_array() [strange] - hellomen - 10-29-2013
(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
RE: Issue with in_array() [strange] - 1llusion - 10-29-2013
(10-29-2013, 12:48 AM)hellomen Wrote:(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
oh wait, my bad
sorry, when talking about file uploads I automatically assume you are saving them 
hmm, I'm sure we could find some vulns there anyway
RE: Issue with in_array() [strange] - 1llusion - 10-29-2013
(10-29-2013, 12:48 AM)hellomen Wrote:(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
oh wait, my bad
sorry, when talking about file uploads I automatically assume you are saving them hmm, I'm sure we could find some vulns there anyway
RE: Issue with in_array() [strange] - 1llusion - 10-29-2013
(10-29-2013, 12:48 AM)hellomen Wrote:(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
oh wait, my bad
sorry, when talking about file uploads I automatically assume you are saving them hmm, I'm sure we could find some vulns there anyway
RE: Issue with in_array() [strange] - 1llusion - 10-29-2013
(10-29-2013, 12:48 AM)hellomen Wrote:(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
oh wait, my bad
sorry, when talking about file uploads I automatically assume you are saving them hmm, I'm sure we could find some vulns there anyway
RE: Issue with in_array() [strange] - 1llusion - 10-29-2013
(10-29-2013, 12:48 AM)hellomen Wrote:(10-29-2013, 12:34 AM)1llusion Wrote:be aware it doesn't save the files on the web server itselves(10-29-2013, 12:26 AM)hellomen Wrote: it is accepting: image/jpg image/jpeg and image/gif which are mime types
all other types are yet blocked out...
Unless you changed the way you check for this stuff, it is still vulnerable.
Best explanation is here (also with good pointers): http://security.stackexchange.com/questions/32852/risks-of-a-php-image-upload-form
it saves it in a database those vulnerabilities are for webserver savement
the BLOB on a database also only allows images so whenever the user tries to bypass part one the database says hehe this is not worthly for the blob row
oh wait, my bad
sorry, when talking about file uploads I automatically assume you are saving them hmm, I'm sure we could find some vulns there anyway