4.3 CVE-2025-3037

CSRF
 

A vulnerability has been found in yzk2356911358 StudentServlet-JSP cc0cdce25fbe43b6c58b60a77a2c85f52d2102f5/d4d7a0643f1dae908a4831206f2714b21820f991 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.
https://nvd.nist.gov/vuln/detail/CVE-2025-3037

Categories

CWE-352 : Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. CSRF is currently difficult to detect reliably using automated techniques. This is because each application has its own implicit security policy that dictates which requests can be influenced by an outsider and automatically performed on behalf of a user, versus which requests require strong confidence that the user intends to make the request. For example, a keyword search of the public portion of a web site is typically expected to be encoded within a link that can be launched automatically when the user clicks on the link. Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script. Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332] Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation. Do not use the GET method for any request that triggers a state change. Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons. Add user accounts via a URL in an img tag Add user accounts via a URL in an img tag Arbitrary code execution by specifying the code in a crafted img tag or URL Gain administrative privileges via a URL in an img tag Delete a victim's information via a URL or an img tag Change another user's settings via a URL or an img tag Perform actions as administrator via a URL or an img tag modify password for the administrator CMS allows modification of configuration via CSRF attack against the administrator web interface allows password changes or stopping a virtual machine via CSRF

References


 

CPE

cpe start end


REMEDIATION




EXPLOITS


Exploit-db.com

id description date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits


CAPEC


Common Attack Pattern Enumerations and Classifications

id description severity
111 JSON Hijacking (aka JavaScript Hijacking)
High
462 Cross-Domain Search Timing
Medium
467 Cross Site Identification
Low
62 Cross Site Request Forgery
Very High