API tools faq
paste
Advertisement
Guest User

Pmsclan.com Hacked

a guest
Apr 24th, 2014
45
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 20.60 KB | None | 0 0
raw download clone embed print report
  1. [+] [16] Trusted -- Interesting response
  2. [~] ~~~~~~~~~~~~~~~~~~~~
  3. [~] ID Hash: 3fe201a5149d8890580c4d9ccd500f7de68deba73500c08d8481eca0582829b3
  4. [~] Severity: Informational
  5. [~] URL: http://pmsclan.com/data/
  6. [~] Element: server
  7. [~] Method: GET
  8. [~] Tags: interesting, response, server
  9. [~] Description:
  10. [~] The server responded with a non 200 (OK) nor 404
  11. (Not Found) status code. This is a non-issue, however exotic HTTP
  12. response status codes can provide useful insights into the behavior
  13. of the web application and assist with the penetration test.
  14.  
  15. [~] Requires manual verification?: false
  16.  
  17. [~] References:
  18. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  19.  
  20. [*] Variations
  21. [~] ----------
  22. [~] Variation 1:
  23. [~] URL: http://pmsclan.com/data/
  24. [~] ID: Code: 403
  25. [~] Regular expression:
  26.  
  27. [+] [17] Trusted -- Interesting response
  28. [~] ~~~~~~~~~~~~~~~~~~~~
  29. [~] ID Hash: bca7f0304f05d172bc4efb77d84961aded358bacae8fa038f3b0ee1134c092b4
  30. [~] Severity: Informational
  31. [~] URL: http://pmsclan.com/administrator/
  32. [~] Element: server
  33. [~] Method: GET
  34. [~] Tags: interesting, response, server
  35. [~] Description:
  36. [~] The server responded with a non 200 (OK) nor 404
  37. (Not Found) status code. This is a non-issue, however exotic HTTP
  38. response status codes can provide useful insights into the behavior
  39. of the web application and assist with the penetration test.
  40.  
  41. [~] Requires manual verification?: false
  42.  
  43. [~] References:
  44. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  45.  
  46. [*] Variations
  47. [~] ----------
  48. [~] Variation 1:
  49. [~] URL: http://pmsclan.com/administrator/
  50. [~] ID: Code: 403
  51. [~] Regular expression:
  52.  
  53. [+] [18] Trusted -- Interesting response
  54. [~] ~~~~~~~~~~~~~~~~~~~~
  55. [~] ID Hash: 2d8a0355cc1b766e99c925cc6370b90687e53751d90c1a02f8fb641d2c92e420
  56. [~] Severity: Informational
  57. [~] URL: http://pmsclan.com/
  58. [~] Element: server
  59. [~] Method: TRACE
  60. [~] Tags: interesting, response, server
  61. [~] Description:
  62. [~] The server responded with a non 200 (OK) nor 404
  63. (Not Found) status code. This is a non-issue, however exotic HTTP
  64. response status codes can provide useful insights into the behavior
  65. of the web application and assist with the penetration test.
  66.  
  67. [~] Requires manual verification?: false
  68.  
  69. [~] References:
  70. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  71.  
  72. [*] Variations
  73. [~] ----------
  74. [~] Variation 1:
  75. [~] URL: http://pmsclan.com/
  76. [~] ID: Code: 405
  77. [~] Regular expression:
  78.  
  79. [+] [19] Trusted -- Interesting response
  80. [~] ~~~~~~~~~~~~~~~~~~~~
  81. [~] ID Hash: 71db2090c40e9a6ffb6519dfc7a4af9614ab37067a7bc237696e3df397073011
  82. [~] Severity: Informational
  83. [~] URL: http://pmsclan.com/Arachni-7db2c
  84. [~] Element: server
  85. [~] Method: PUT
  86. [~] Tags: interesting, response, server
  87. [~] Description:
  88. [~] The server responded with a non 200 (OK) nor 404
  89. (Not Found) status code. This is a non-issue, however exotic HTTP
  90. response status codes can provide useful insights into the behavior
  91. of the web application and assist with the penetration test.
  92.  
  93. [~] Requires manual verification?: false
  94.  
  95. [~] References:
  96. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  97.  
  98. [*] Variations
  99. [~] ----------
  100. [~] Variation 1:
  101. [~] URL: http://pmsclan.com/Arachni-7db2c
  102. [~] ID: Code: 405
  103. [~] Regular expression:
  104.  
  105. [+] [20] Trusted -- HttpOnly cookie
  106. [~] ~~~~~~~~~~~~~~~~~~~~
  107. [~] ID Hash: 604a45c7d671568474fc81cba3c2a697c9773a90d0013bae04abcdd435bb43f0
  108. [~] Severity: Informational
  109. [~] URL: http://pmsclan.com/forum/
  110. [~] Element: cookie
  111. [~] Method: GET
  112. [~] Tags:
  113. [~] Variable: bblastactivity
  114. [~] Description:
  115. [~] HTTP by itself is a stateless protocol.
  116. Therefor the server is unable to determine which requests
  117. are performed by which client, and which clients are
  118. authenticated or unauthenticated. The use of HTTP cookies
  119. within the headers, allows a web server to identify each
  120. individual client, and can therefor determine which clients
  121. hold valid authentication from those that do not. These are
  122. known as session cookies. When a cookie is set by the server
  123. there are several flags that can be set to configure the
  124. properties of the cookie, and how it is handled by the browser.
  125. The HttpOnly flag assists in the prevention of client side
  126. scripts (such as JavaScript) accessing, and using the cookie.
  127. This can help preventing XSS attacks targeting the cookies
  128. holding the clients session token (Setting the HttpOnly flag
  129. does not prevent, or remediate against XSS vulnerabilities
  130. themselves).
  131.  
  132. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  133.  
  134. [~] Requires manual verification?: false
  135.  
  136. [~] References:
  137. [~] OWASP - https://www.owasp.org/index.php/HttpOnly
  138.  
  139. [*] Variations
  140. [~] ----------
  141. [~] Variation 1:
  142. [~] URL: http://pmsclan.com/forum/
  143. [~] Regular expression:
  144.  
  145. [+] [21] Trusted -- HttpOnly cookie
  146. [~] ~~~~~~~~~~~~~~~~~~~~
  147. [~] ID Hash: 0026dde47e245e82864e8d9f06cbb979c243dceeea8f92343a86f444806ea27c
  148. [~] Severity: Informational
  149. [~] URL: http://pmsclan.com/forum/
  150. [~] Element: cookie
  151. [~] Method: GET
  152. [~] Tags:
  153. [~] Variable: bblastvisit
  154. [~] Description:
  155. [~] HTTP by itself is a stateless protocol.
  156. Therefor the server is unable to determine which requests
  157. are performed by which client, and which clients are
  158. authenticated or unauthenticated. The use of HTTP cookies
  159. within the headers, allows a web server to identify each
  160. individual client, and can therefor determine which clients
  161. hold valid authentication from those that do not. These are
  162. known as session cookies. When a cookie is set by the server
  163. there are several flags that can be set to configure the
  164. properties of the cookie, and how it is handled by the browser.
  165. The HttpOnly flag assists in the prevention of client side
  166. scripts (such as JavaScript) accessing, and using the cookie.
  167. This can help preventing XSS attacks targeting the cookies
  168. holding the clients session token (Setting the HttpOnly flag
  169. does not prevent, or remediate against XSS vulnerabilities
  170. themselves).
  171.  
  172. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  173.  
  174. [~] Requires manual verification?: false
  175.  
  176. [~] References:
  177. [~] OWASP - https://www.owasp.org/index.php/HttpOnly
  178.  
  179. [*] Variations
  180. [~] ----------
  181. [~] Variation 1:
  182. [~] URL: http://pmsclan.com/forum/
  183. [~] Regular expression:
  184.  
  185. [+] [22] Trusted -- Insecure cookie
  186. [~] ~~~~~~~~~~~~~~~~~~~~
  187. [~] ID Hash: 11539ec3689960a8bb6242d258017686481ce7339b8706a8bd825269c99e0716
  188. [~] Severity: Informational
  189. [~] URL: http://pmsclan.com/forum/
  190. [~] Element: cookie
  191. [~] Method: GET
  192. [~] Tags:
  193. [~] Variable: bblastactivity
  194. [~] Description:
  195. [~] HTTP by itself is a stateless protocol.
  196. Therefore the server is unable to determine which requests
  197. are performed by which client, and which clients are
  198. authenticated or unauthenticated. The use of HTTP cookies
  199. within the headers, allows a web server to identify each
  200. individual client, and can therefore determine which clients
  201. hold valid authentication from those that do not. These are
  202. known as session cookies. Because these cookies are used to
  203. store a client's session (authenticated or unauthenticated),
  204. it is important that the cookie is passed via an encrypted
  205. channel. When a cookie is set by the server (send from the
  206. server to the client in the header of response) there are
  207. several flags that can be set to determine the properties of
  208. the cookie, and how it is to handle by the browser. One of
  209. these flags is known as the 'secure' flag. When the secure
  210. flag is set, the browser will prevent it being send over any
  211. clear text channel (HTTP), and only allow it to be sent when
  212. an encrypted channel is used (HTTPS). Arachni discovered
  213. that a cookie, and possible session token was set by the
  214. server without the secure flag being set. Although the
  215. initial setting of this cookie was via an HTTPS connection,
  216. any HTTP link to the same server will result in the cookie
  217. being send in clear text.
  218.  
  219. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  220.  
  221. [~] Requires manual verification?: false
  222.  
  223. [~] References:
  224. [~] OWASP - https://www.owasp.org/index.php/SecureFlag
  225.  
  226. [*] Variations
  227. [~] ----------
  228. [~] Variation 1:
  229. [~] URL: http://pmsclan.com/forum/
  230. [~] Regular expression:
  231.  
  232. [+] [23] Trusted -- Insecure cookie
  233. [~] ~~~~~~~~~~~~~~~~~~~~
  234. [~] ID Hash: 8121cc9139c5937eeb20d394808bb9765dcd11234f1da0b03d5b8429ce637999
  235. [~] Severity: Informational
  236. [~] URL: http://pmsclan.com/forum/
  237. [~] Element: cookie
  238. [~] Method: GET
  239. [~] Tags:
  240. [~] Variable: bblastvisit
  241. [~] Description:
  242. [~] HTTP by itself is a stateless protocol.
  243. Therefore the server is unable to determine which requests
  244. are performed by which client, and which clients are
  245. authenticated or unauthenticated. The use of HTTP cookies
  246. within the headers, allows a web server to identify each
  247. individual client, and can therefore determine which clients
  248. hold valid authentication from those that do not. These are
  249. known as session cookies. Because these cookies are used to
  250. store a client's session (authenticated or unauthenticated),
  251. it is important that the cookie is passed via an encrypted
  252. channel. When a cookie is set by the server (send from the
  253. server to the client in the header of response) there are
  254. several flags that can be set to determine the properties of
  255. the cookie, and how it is to handle by the browser. One of
  256. these flags is known as the 'secure' flag. When the secure
  257. flag is set, the browser will prevent it being send over any
  258. clear text channel (HTTP), and only allow it to be sent when
  259. an encrypted channel is used (HTTPS). Arachni discovered
  260. that a cookie, and possible session token was set by the
  261. server without the secure flag being set. Although the
  262. initial setting of this cookie was via an HTTPS connection,
  263. any HTTP link to the same server will result in the cookie
  264. being send in clear text.
  265.  
  266. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  267.  
  268. [~] Requires manual verification?: false
  269.  
  270. [~] References:
  271. [~] OWASP - https://www.owasp.org/index.php/SecureFlag
  272.  
  273. [*] Variations
  274. [~] ----------
  275. [~] Variation 1:
  276. [~] URL: http://pmsclan.com/forum/
  277. [~] Regular expression:
  278.  
  279. [+] [24] Trusted -- Insecure cookie
  280. [~] ~~~~~~~~~~~~~~~~~~~~
  281. [~] ID Hash: 5a92cf32bf2a6e498ff943e95e0214138a4d47455e5511a96a6545461ebcb708
  282. [~] Severity: Informational
  283. [~] URL: http://pmsclan.com/forum/
  284. [~] Element: cookie
  285. [~] Method: GET
  286. [~] Tags:
  287. [~] Variable: bbsessionhash
  288. [~] Description:
  289. [~] HTTP by itself is a stateless protocol.
  290. Therefore the server is unable to determine which requests
  291. are performed by which client, and which clients are
  292. authenticated or unauthenticated. The use of HTTP cookies
  293. within the headers, allows a web server to identify each
  294. individual client, and can therefore determine which clients
  295. hold valid authentication from those that do not. These are
  296. known as session cookies. Because these cookies are used to
  297. store a client's session (authenticated or unauthenticated),
  298. it is important that the cookie is passed via an encrypted
  299. channel. When a cookie is set by the server (send from the
  300. server to the client in the header of response) there are
  301. several flags that can be set to determine the properties of
  302. the cookie, and how it is to handle by the browser. One of
  303. these flags is known as the 'secure' flag. When the secure
  304. flag is set, the browser will prevent it being send over any
  305. clear text channel (HTTP), and only allow it to be sent when
  306. an encrypted channel is used (HTTPS). Arachni discovered
  307. that a cookie, and possible session token was set by the
  308. server without the secure flag being set. Although the
  309. initial setting of this cookie was via an HTTPS connection,
  310. any HTTP link to the same server will result in the cookie
  311. being send in clear text.
  312.  
  313. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  314.  
  315. [~] Requires manual verification?: false
  316.  
  317. [~] References:
  318. [~] OWASP - https://www.owasp.org/index.php/SecureFlag
  319.  
  320. [*] Variations
  321. [~] ----------
  322. [~] Variation 1:
  323. [~] URL: http://pmsclan.com/forum/
  324. [~] Regular expression:
  325.  
  326. [+] [25] Trusted -- Interesting response
  327. [~] ~~~~~~~~~~~~~~~~~~~~
  328. [~] ID Hash: 16b09c0269d704236335efe32bd3efdfff3da6a7ee3eab7c7682f1ca03d96f3f
  329. [~] Severity: Informational
  330. [~] URL: http://pmsclan.com/forum/Arachni-7db2c
  331. [~] Element: server
  332. [~] Method: PUT
  333. [~] Tags: interesting, response, server
  334. [~] Description:
  335. [~] The server responded with a non 200 (OK) nor 404
  336. (Not Found) status code. This is a non-issue, however exotic HTTP
  337. response status codes can provide useful insights into the behavior
  338. of the web application and assist with the penetration test.
  339.  
  340. [~] Requires manual verification?: false
  341.  
  342. [~] References:
  343. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  344.  
  345. [*] Variations
  346. [~] ----------
  347. [~] Variation 1:
  348. [~] URL: http://pmsclan.com/forum/Arachni-7db2c
  349. [~] ID: Code: 405
  350. [~] Regular expression:
  351.  
  352. [+] [26] Trusted -- HTML object
  353. [~] ~~~~~~~~~~~~~~~~~~~~
  354. [~] ID Hash: c5437e9fcff9773de9ed246f65409f836abcef012925e01aa0a7b43b5f4098a6
  355. [~] Severity: Informational
  356. [~] URL: http://pmsclan.com/js/ufo.js
  357. [~] Element: body
  358. [~] Method: GET
  359. [~] Tags:
  360. [~] Description:
  361. [~] Logs the existence of HTML object tags.
  362. Since Arachni can't execute things like Java Applets and Flash
  363. this serves as a heads-up to the penetration tester to review
  364. the objects in question using a different method.
  365.  
  366. [~] CWE: http://cwe.mitre.org/data/definitions/200.html
  367.  
  368. [~] Requires manual verification?: false
  369.  
  370. [~] References:
  371.  
  372. [*] Variations
  373. [~] ----------
  374. [~] Variation 1:
  375. [~] URL: http://pmsclan.com/js/ufo.js
  376. [~] Regular expression: (?mi-x:<object(.*)>(.*)<\/object>)
  377. [~] Matched string: classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"' + _objAtt + ' width="' + _fo.width + '" height="' + _fo.height + '" codebase="' + _p + '//download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=' + _fo.majorversion + ',0,' + _fo.build + ',0"><param name="movie" value="' + _fo.movie + '" /
  378. [~] Variation 2:
  379. [~] URL: http://pmsclan.com/js/ufo.js
  380. [~] Regular expression: (?mi-x:<object(.*)>(.*)<\/object>)
  381. [~] Matched string: ' + _objPar + '
  382.  
  383. [+] [27] Trusted -- Interesting response
  384. [~] ~~~~~~~~~~~~~~~~~~~~
  385. [~] ID Hash: 8aecd4e4bee930ec05aa75910167814dba1659d59b38559bb3fd1dcdd0f2ba03
  386. [~] Severity: Informational
  387. [~] URL: http://pmsclan.com/js/?%3E%22&#039;%3E%3Cmy_tag_7db2cb1a171eda8e5e5b3f3f4dfa522a1ff16d8796d6e82669b5c9d652ab7f19/%3E=
  388. [~] Element: server
  389. [~] Method: GET
  390. [~] Tags: interesting, response, server
  391. [~] Description:
  392. [~] The server responded with a non 200 (OK) nor 404
  393. (Not Found) status code. This is a non-issue, however exotic HTTP
  394. response status codes can provide useful insights into the behavior
  395. of the web application and assist with the penetration test.
  396.  
  397. [~] Requires manual verification?: false
  398.  
  399. [~] References:
  400. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  401.  
  402. [*] Variations
  403. [~] ----------
  404. [~] Variation 1:
  405. [~] URL: http://pmsclan.com/js/?%3E%22&#039;%3E%3Cmy_tag_7db2cb1a171eda8e5e5b3f3f4dfa522a1ff16d8796d6e82669b5c9d652ab7f19/%3E=
  406. [~] ID: Code: 403
  407. [~] Regular expression:
  408.  
  409. [+] [28] Trusted -- Interesting response
  410. [~] ~~~~~~~~~~~~~~~~~~~~
  411. [~] ID Hash: 5c88eb93b19ab8aaa8e9997f469823ee3e1217afb03cb081a862bf2bf597b464
  412. [~] Severity: Informational
  413. [~] URL: http://pmsclan.com/js/Arachni-7db2c
  414. [~] Element: server
  415. [~] Method: PUT
  416. [~] Tags: interesting, response, server
  417. [~] Description:
  418. [~] The server responded with a non 200 (OK) nor 404
  419. (Not Found) status code. This is a non-issue, however exotic HTTP
  420. response status codes can provide useful insights into the behavior
  421. of the web application and assist with the penetration test.
  422.  
  423. [~] Requires manual verification?: false
  424.  
  425. [~] References:
  426. [~] w3.org - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  427.  
  428. [*] Variations
  429. [~] ----------
  430. [~] Variation 1:
  431. [~] URL: http://pmsclan.com/js/Arachni-7db2c
  432. [~] ID: Code: 405
  433. [~] Regular expression:
  434.  
  435.  
  436. [+] Plugin data:
  437. [~] ---------------
  438.  
  439.  
  440. [*] Health map
  441. [~] ~~~~~~~~~~~~~~
  442. [~] Description: Generates a simple list of safe/unsafe URLs.
  443.  
  444. [~] Legend:
  445. [+] No issues
  446. [-] Has issues
  447.  
  448. [-] http://pmsclan.com/
  449. [+] http://pmsclan.com/favicon.ico
  450. [-] http://pmsclan.com/forum/
  451. [+] http://pmsclan.com/forum/forumdisplay.php
  452. [+] http://pmsclan.com/forum/index.php
  453. [+] http://pmsclan.com/forum/login.php
  454. [+] http://pmsclan.com/forum/search.php
  455. [-] http://pmsclan.com/js/ufo.js
  456. [-] http://pmsclan.com/forum/login.php?do=login
  457. [-] http://pmsclan.com/forum/archive/
  458. [-] http://pmsclan.com/robots.txt
  459. [-] http://pmsclan.com/cgi-bin/
  460. [-] http://pmsclan.com/cache/
  461. [-] http://pmsclan.com/classes/
  462. [-] http://pmsclan.com/data/
  463. [-] http://pmsclan.com/administrator/
  464. [-] http://pmsclan.com/Arachni-7db2c
  465. [-] http://pmsclan.com/forum/Arachni-7db2c
  466. [-] http://pmsclan.com/js/?%3E%22&#039;%3E%3Cmy_tag_7db2cb1a171eda8e5e5b3f3f4dfa522a1ff16d8796d6e82669b5c9d652ab7f19/%3E=
  467. [-] http://pmsclan.com/js/Arachni-7db2c
  468.  
  469. [~] Total: 20
  470. [+] Without issues: 5
  471. [-] With issues: 15 ( 75% )
  472.  
  473. [*] Resolver
  474. [~] ~~~~~~~~~~~~~~
  475. [~] Description: Resolves vulnerable hostnames to IP addresses.
  476.  
  477. [~] pmsclan.com: 216.58.155.70
  478.  
  479. [*] Uniformity (Lack of central sanitization)
  480. [~] ~~~~~~~~~~~~~~
  481. [~] Description: Analyzes the scan results and logs issues which persist across different pages.
  482. This is usually a sign for a lack of a central/single point of input sanitization,
  483. a bad coding practise.
  484.  
  485. [~] Relevant issues:
  486. [~] --------------------
  487. [+] Unencrypted password form in form variable 'vb_login_password' using GET at the following pages:
  488. [~] http://pmsclan.com/ (Issue #3 - Hash ID: 94277c626f906fb11e1b8aac662022ef42f6038373ac7626132f5cae248c4f49 )
  489. [~] http://pmsclan.com/forum/ (Issue #5 - Hash ID: c30432a029a25c047826a157a6117dac0fafdf2a42c60ef25859717ec12d9c1e )
  490.  
  491.  
  492. [~] 100.0% [============================================================>] 100%
  493. [~] Est. remaining time: 00:00:00
  494.  
  495. [~] Crawler has discovered 18 pages.
  496.  
  497. [~] Sent 13472 requests.
  498. [~] Received and analyzed 13472 responses.
  499. [~] In 02:51:45
  500. [~] Average: 1 requests/second.
  501.  
  502. [~] Currently auditing http://pmsclan.com/js/ufo.js
  503. [~] Burst response time total 0
  504. [~] Burst response count total 0
  505. [~] Burst average response time 0
  506. [~] Burst average 0 requests/second
  507. [~] Timed-out requests 468
  508. [~] Original max concurrency 20
  509. [~] Throttled max concurrency 20
  510.  
  511. by n0 1dentity - Phoenix. Get shitted on PMSCLAN.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!