Notice
Recent Posts
Recent Comments
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 |
Tags
- idb2pat
- Python
- idapro
- NumPy Unicode Error
- x64
- Rat
- malware
- Ransomware
- mock.patch
- 포인터 매핑
- Analysis
- ida
- hex-rays
- commandline
- debugging
- ecma
- ida pro
- h5py.File
- error
- data distribution
- TensorFlow
- Injection
- javascript
- pytest
- why error
- idapython
- error fix
- open office xml
- svn update
- MySQL
Archives
- Today
- Total
목록bracket (1)
13 Security Lab
![](http://i1.daumcdn.net/thumb/C150x150/?fname=https://blog.kakaocdn.net/dn/UeUVj/btqYpXL49Fb/qm2Ub5xV4DqO4Xod4VL5Ak/img.png)
Do not use SQL parameters for table names. SQL parameters are escaped by the database adapter to not be interpreted as anything but literal values. You'll have to interpolate those yourself instead, but be absolutely certain that your table name does not hold untrusted data (prevent SQL injection attacks): 1 2 cur.execute("GRANT SELECT ON `project1`.`%s` TO `odbc`@`localhost`;" % row) cur.execut..
Computer Science/Programming
2015. 12. 4. 18:00