Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-0510: CWE-918 Server-Side Request Forgery in HaoKeKeJi YiQiNiu

0
High
VulnerabilityCVE-2024-0510cvecve-2024-0510cwe-918
Published: Sat Jan 13 2024 (01/13/2024, 22:00:06 UTC)
Source: CVE
Vendor/Project: HaoKeKeJi
Product: YiQiNiu

Description

A vulnerability, which was classified as critical, has been found in HaoKeKeJi YiQiNiu up to 3.1. Affected by this issue is the function http_post of the file /application/pay/controller/Api.php. The manipulation of the argument url leads to server-side request forgery. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250652.

AI-Powered Analysis

AILast updated: 11/04/2025, 23:58:08 UTC

Technical Analysis

CVE-2024-0510 is a server-side request forgery (SSRF) vulnerability classified under CWE-918, affecting HaoKeKeJi YiQiNiu versions 3.0 and 3.1. The vulnerability resides in the http_post function of the /application/pay/controller/Api.php file, where the 'url' parameter is insufficiently validated, allowing an attacker to manipulate it to force the server to initiate arbitrary HTTP requests. SSRF vulnerabilities enable attackers to make the server perform requests to internal or external systems, potentially bypassing firewall restrictions and accessing sensitive internal services or metadata endpoints. This can lead to information disclosure, unauthorized actions, or denial of service. The vulnerability can be exploited remotely without requiring authentication or user interaction, increasing the attack surface. The CVSS v3.1 score of 7.3 reflects high severity, with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The lack of available patches necessitates immediate mitigation through input validation, network segmentation, and monitoring outbound requests. Organizations using YiQiNiu, especially in payment processing or API integrations, should assess their exposure and implement controls to prevent exploitation.

Potential Impact

For European organizations, the impact of CVE-2024-0510 can be significant, particularly for those relying on HaoKeKeJi YiQiNiu for payment processing or API services. Exploitation of this SSRF vulnerability could allow attackers to access internal network resources that are otherwise protected by firewalls, leading to potential data breaches or lateral movement within the network. Confidential information such as internal APIs, databases, or cloud metadata services could be exposed, compromising data confidentiality and integrity. Additionally, attackers could leverage the vulnerability to disrupt services, causing denial of service conditions impacting availability. The ability to launch attacks remotely without authentication increases the risk profile for organizations. Given the criticality of payment systems and the sensitivity of financial data, exploitation could result in regulatory penalties under GDPR and damage to organizational reputation. The vulnerability also poses risks to supply chain security if YiQiNiu is integrated into third-party services used by European enterprises.

Mitigation Recommendations

To mitigate CVE-2024-0510, European organizations should implement the following specific measures: 1) Apply strict input validation and sanitization on the 'url' parameter in the http_post function to ensure only legitimate and expected URLs are processed. 2) Implement an allowlist of approved domains or IP addresses for outbound HTTP requests initiated by the application to prevent arbitrary external or internal requests. 3) Employ network segmentation and firewall rules to restrict the server’s ability to access sensitive internal resources or metadata endpoints, limiting the impact of SSRF exploitation. 4) Monitor and log outbound HTTP requests from the application to detect anomalous or unauthorized access attempts. 5) If possible, update or patch the YiQiNiu product once an official fix is released by the vendor. 6) Conduct security assessments and penetration testing focusing on SSRF vectors within the application environment. 7) Educate development and operations teams about SSRF risks and secure coding practices to prevent similar vulnerabilities in future releases.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2024-01-12T19:13:38.339Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682cd0fb1484d88663aeca21

Added to database: 5/20/2025, 6:59:07 PM

Last enriched: 11/4/2025, 11:58:08 PM

Last updated: 12/4/2025, 5:48:40 AM

Views: 41

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats