CVE-2025-10252
BaseFortify
Publication date: 2025-09-11
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| seat | queue_ticket_kiosk | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10252 is a deserialization vulnerability in the SEAT Queue Ticket Kiosk software (up to version 20250827) affecting the Java RMI Registry Handler component. It allows an attacker within the local network to manipulate untrusted input to perform unsafe deserialization, potentially compromising confidentiality. Exploitation is difficult and does not require authentication. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker on the local network to deserialize malicious data, potentially leading to unauthorized access to confidential information. While it does not affect integrity or availability, it may expose sensitive data. Exploitation is considered difficult, and mitigation involves restricting local network access to the vulnerable service. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve enumerating the Java RMI Registry to identify exposed remote objects. Tools like Remote Method Guesser can be used to perform this enumeration, revealing bound object names, interface types, and endpoint information. This helps identify if the vulnerable Java RMI Registry Handler is accessible within the local network. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying restrictive firewall rules to limit access to the vulnerable Java RMI Registry Handler service from the local network. Since exploitation requires local network access and is difficult, restricting network access reduces the attack surface. No vendor patch is available as the vendor did not respond. [1]