IHmG

Untitled

Apr 26th, 2023
120
0
Never
5
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.42 KB | None | 0 0
  1. Trace file C:\ORACLE\diag\rdbms\kesdev2\kesdev2\trace\kesdev2_ora_5064.trc
  2. Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
  3. Version 19.3.0.0.0
  4. Build label: RDBMS_19.3.0.0.0DBRU_WINDOWS.X64_190528
  5. Windows NT Version V6.2
  6. ORACLE_HOME = C:\Oracle\product\19.3.0\dbhome_1
  7. Node name : KES-SDBS61
  8. CPU : 2 - type 86642 physical cores
  9. Process Affinity : 0x0000000000000000
  10. Memory (Avail/Total): Ph:11441M/20478M, Ph+PgF:16527M/25478M
  11. VM name : VMWare Version (6)
  12. Instance name: kesdev2
  13. Redo thread mounted by this instance: 1
  14. Oracle process number: 66
  15. Windows thread id: 5064, image: ORACLE.EXE (SHAD)
  16.  
  17.  
  18. *** 2023-04-27T11:54:08.902831+07:00 (BRIS(3))
  19. *** SESSION ID:(48.31579) 2023-04-27T11:54:08.902831+07:00
  20. *** CLIENT ID:() 2023-04-27T11:54:08.902831+07:00
  21. *** SERVICE NAME:(bris) 2023-04-27T11:54:08.902831+07:00
  22. *** MODULE NAME:(/about/changelog) 2023-04-27T11:54:08.902831+07:00
  23. *** ACTION NAME:(GET) 2023-04-27T11:54:08.902831+07:00
  24. *** CLIENT DRIVER:(jdbcthin : 21.1.0.0.0) 2023-04-27T11:54:08.902831+07:00
  25. *** CONTAINER ID:(3) 2023-04-27T11:54:08.902831+07:00
  26.  
  27. dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=1, mask=0x0)
  28. ----- Error Stack Dump -----
  29. <error barrier> at 0x0000009DD2DB1ED0 placed dbkda.c@296
  30. ORA-29263: ошибка протокола HTTP
  31. ----- Current SQL Statement for this session (sql_id=1d37gxjt4n480) -----
  32. DECLARE
  33. V_NUM NUMBER;
  34. BEGIN
  35. V_NUM := BRIS.LOGGER_PKG.LOG_QUERY_START();
  36. BRIS.API_GET_ABOUT_CHANGELOG;
  37. BRIS.LOGGER_PKG.LOG_QUERY_END(P_IN_ID => V_NUM);
  38. EXCEPTION
  39. WHEN BRIS.CONST_PKG.E_DATA_CONFLICT THEN
  40. ROLLBACK;
  41. BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_NOT_FOUND);
  42. WHEN BRIS.CONST_PKG.E_INVALID_PARAMETER THEN
  43. BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_BAD_REQUEST);
  44. WHEN BRIS.CONST_PKG.E_INVALID_LOGICAL_BEHAVIOR THEN
  45. BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_BAD_REQUEST_ERROR, SQLERRM, UTL_HTTP.HTTP_BAD_REQUEST);
  46. WHEN BRIS.CONST_PKG.E_FORBIDDEN THEN
  47. BRIS.RESULTS_PKG.FORM_JSON_ERROR(BRIS.CONST_PKG.CODE_FORBIDDEN_ERROR, SQLERRM, UTL_HTTP.HTTP_FORBIDDEN);
  48. WHEN OTHERS THEN
  49. BRIS.LOGGER_PKG.ERROR;
  50. BRIS.RESULTS_PKG.FORM_JSON_SERVER_ERROR;
  51. END;
  52. ----- PL/SQL Stack -----
  53. ----- PL/SQL Call Stack -----
  54. object line object
  55. handle number name
  56. 00007FFAD51449A8 837 package body SYS.UTL_HTTP.READ_TEXT
  57. 00007FFAD51449A8 1350 package body SYS.UTL_HTTP.READ_TEXT
  58. 00007FFADD5F8420 551 package body BRIS.HTTP_PKG.GET_FILE_CONTENT
  59. 00007FFB0E7DC858 36 procedure BRIS.API_GET_ABOUT_CHANGELOG
  60. 00007FFB206D4528 7 anonymous block
  61.  
  62. ----- Call Stack Trace -----
  63. calling call entry argument values in hex
  64. location type point (? means dubious value)
  65. -------------------- -------- -------------------- ----------------------------
  66. ksedst()+89 CALL??? ksedst1() 000000000 000000001
  67. 000000000 ? 000000000 ?
  68. dbkedDefDump()+2289 CALL??? ksedst() 000000000 000000000 ?
  69. 000000000 ? 000000000 ?
  70. ksedmp()+329 CALL??? dbkedDefDump() 000000001 000000000
  71.  
Advertisement
Comments
  • User was banned
  • User was banned
  • User was banned
  • Ulrjutir
    81 days
    # CSS 0.85 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1dOCZEHS5JtM51RITOJzbS4o3hZ-__wTTRXQkV1MexNQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
  • User was banned
Add Comment
Please, Sign In to add comment