{"vulnerability": "CVE-2019-2502", "sightings": [{"uuid": "47214452-30d8-4ff3-bb7f-182b4199cd69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25024", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3m76umsssim2b", "content": "", "creation_timestamp": "2025-12-04T21:02:33.495172Z"}, {"uuid": "be9cd551-538c-46ff-a453-277d9cdc3632", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-2502", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5991", "content": "PRION:CVE-2019-2510     4.0     https://vulners.com/prion/PRION:CVE-2019-2510               |       PRION:CVE-2019-2507     4.0     https://vulners.com/prion/PRION:CVE-2019-2507               |       PRION:CVE-2019-2502     4.0     https://vulners.com/prion/PRION:CVE-2019-2502               |       PRION:CVE-2019-2495     4.0     https://vulners.com/prion/PRION:CVE-2019-2495               |       PRION:CVE-2019-2494     4.0     https://vulners.com/prion/PRION:CVE-2019-2494               |       PRION:CVE-2019-2486     4.0     https://vulners.com/prion/PRION:CVE-2019-2486               |       PRION:CVE-2019-2482     4.0     https://vulners.com/prion/PRION:CVE-2019-2482               |       PRION:CVE-2019-2481     4.0     https://vulners.com/prion/PRION:CVE-2019-2481               |       PRION:CVE-2019-2455     4.0     https://vulners.com/prion/PRION:CVE-2019-2455               |       PRION:CVE-2019-2434     4.0     https://vulners.com/prion/PRION:CVE-2019-2434               |       PRION:CVE-2019-2420     4.0     https://vulners.com/prion/PRION:CVE-2019-2420               |       PRION:CVE-2018-3286     4.0     https://vulners.com/prion/PRION:CVE-2018-3286               |       PRION:CVE-2018-3285     4.0     https://vulners.com/prion/PRION:CVE-2018-3285               |       PRION:CVE-2018-3282     4.0     https://vulners.com/prion/PRION:CVE-2018-3282               |       PRION:CVE-2018-3280     4.0     https://vulners.com/prion/PRION:CVE-2018-3280               |       PRION:CVE-2018-3279     4.0     https://vulners.com/prion/PRION:CVE-2018-3279               |       PRION:CVE-2018-3278     4.0     https://vulners.com/prion/PRION:CVE-2018-3278\n|       PRION:CVE-2018-3277     4.0     https://vulners.com/prion/PRION:CVE-2018-3277               |       PRION:CVE-2018-3276     4.0     https://vulners.com/prion/PRION:CVE-2018-3276               |       PRION:CVE-2018-3251     4.0     https://vulners.com/prion/PRION:CVE-2018-3251\n|       PRION:CVE-2018-3212     4.0     https://vulners.com/prion/PRION:CVE-2018-3212               |       PRION:CVE-2018-3203     4.0     https://vulners.com/prion/PRION:CVE-2018-3203               |       PRION:CVE-2018-3200     4.0     https://vulners.com/prion/PRION:CVE-2018-3200               |       PRION:CVE-2018-3186     4.0     https://vulners.com/prion/PRION:CVE-2018-3186               |       PRION:CVE-2018-3182     4.0     https://vulners.com/prion/PRION:CVE-2018-3182               |       PRION:CVE-2018-3173     4.0     https://vulners.com/prion/PRION:CVE-2018-3173\n|       PRION:CVE-2018-3170     4.0     https://vulners.com/prion/PRION:CVE-2018-3170\n|       PRION:CVE-2018-3162     4.0     https://vulners.com/prion/PRION:CVE-2018-3162\n|       PRION:CVE-2018-3161     4.0     https://vulners.com/prion/PRION:CVE-2018-3161               |       PRION:CVE-2018-3156     4.0     https://vulners.com/prion/PRION:CVE-2018-3156               |       PRION:CVE-2018-3155     4.0     https://vulners.com/prion/PRION:CVE-2018-3155               |       PRION:CVE-2018-3145     4.0     https://vulners.com/prion/PRION:CVE-2018-3145               |       PRION:CVE-2018-3143     4.0     https://vulners.com/prion/PRION:CVE-2018-3143               |       PRION:CVE-2018-3137     4.0     https://vulners.com/prion/PRION:CVE-2018-3137               |       PRION:CVE-2018-3133     4.0     https://vulners.com/prion/PRION:CVE-2018-3133               |       PRION:CVE-2018-3082     4.0     https://vulners.com/prion/PRION:CVE-2018-3082               |       PRION:CVE-2018-3080     4.0     https://vulners.com/prion/PRION:CVE-2018-3080\n|       PRION:CVE-2018-3079     4.0     https://vulners.com/prion/PRION:CVE-2018-3079               |       PRION:CVE-2018-3078     4.0     https://vulners.com/prion/PRION:CVE-2018-3078               |       PRION:CVE-2018-3077     4.0     https://vulners.com/prion/PRION:CVE-2018-3077               |       PRION:CVE-2018-3075     4.0     https://vulners.com/prion/PRION:CVE-2018-3075               |       PRION:CVE-2018-3073     4.0     https://vulners.com/prion/PRION:CVE-2018-3073", "creation_timestamp": "2023-11-15T16:53:23.000000Z"}, {"uuid": "de0eeaab-e1c8-4b08-a57b-34acb312bb4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25022", "type": "seen", "source": "https://t.me/cibsecurity/24273", "content": "\u203c CVE-2019-25022 \u203c\n\nAn issue was discovered in Scytl sVote 2.1. An attacker can inject code that gets executed by creating an election-event and injecting a payload over an event alias, because the application calls Runtime.getRuntime().exec() without validation.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-02-27T07:39:57.000000Z"}, {"uuid": "ec25d92b-57ab-4e9f-8191-2a2bde06b4a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25021", "type": "seen", "source": "https://t.me/cibsecurity/24270", "content": "\u203c CVE-2019-25021 \u203c\n\nAn issue was discovered in Scytl sVote 2.1. Due to the implementation of the database manager, an attacker can access the OrientDB by providing admin as the admin password. A different password cannot be set because of the implementation in code.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-02-27T07:39:54.000000Z"}, {"uuid": "0216edb9-0740-4071-842b-2c50d8b9276c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25025", "type": "seen", "source": "https://t.me/cibsecurity/24503", "content": "\u203c CVE-2019-25025 \u203c\n\nThe activerecord-session_store (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-05T12:47:27.000000Z"}, {"uuid": "e89e8822-0ebe-4cb2-88b9-5cb05318e6d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25020", "type": "seen", "source": "https://t.me/cibsecurity/24277", "content": "\u203c CVE-2019-25020 \u203c\n\nAn issue was discovered in Scytl sVote 2.1. Because the sdm-ws-rest API does not require authentication, an attacker can retrieve the administrative configuration by sending a POST request to the /sdm-ws-rest/preconfiguration URI.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-02-27T07:40:04.000000Z"}]}