Ameeba Security Research

Defensive CVE and exploit intelligence

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2024-0510: Critical Server-Side Request Forgery Vulnerability in HaoKeKeJi YiQiNiu

Views: 22

Overview

The cybersecurity community has identified a critical security vulnerability, CVE-2024-0510, in HaoKeKeJi YiQiNiu versions up to 3.1. This vulnerability, which lies in the http_post function of the /application/pay/controller/Api.php file, can lead to server-side request forgery if the URL argument is manipulated. As the exploit is now public knowledge, it presents a significant risk to any organization using the affected software.

Vulnerability Summary

CVE ID: CVE-2024-0510
Severity: Critical (CVSS: 7.3)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise or data leakage

Affected Products

Ameeba Chat Icon Share secrets securely

Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.

Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.

  • • Encrypted identity
  • • Private Spaces for organizations and teams
  • • End-to-end encrypted chat, calls, files, and notes
  • • Sensitive AI work and protected collaboration
  • • Built for information that cannot leak

Our mission is to secure human work alongside AI.

Product | Affected Versions

HaoKeKeJi YiQiNiu | Up to 3.1

How the Exploit Works

The vulnerability arises from improper input validation in the http_post function of the /application/pay/controller/Api.php file in HaoKeKeJi YiQiNiu. By manipulating the ‘url’ argument, an attacker can trick the server into sending a request to any location, potentially leading to unauthorized actions being taken on behalf of the server. This type of vulnerability, known as Server-Side Request Forgery (SSRF), can be used to bypass access controls, perform actions on other internal services, or potentially reveal internal network information.

Conceptual Example Code

The following conceptual HTTP request demonstrates how an attacker might exploit this vulnerability:

POST /application/pay/controller/Api.php HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"url": "http://malicious.example.com/"
}

In this example, the attacker submits a POST request to the vulnerable endpoint, providing a malicious URL in the ‘url’ parameter. The server, failing to validate this input properly, may then send a request to this malicious URL, potentially leading to unauthorized actions or data leakage.

Mitigation Guidance

Organizations are urged to apply the vendor’s patch to mitigate this vulnerability. In the absence of a patch, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can provide temporary mitigation. Regularly updating and patching systems, as well as conducting routine security assessments, can help prevent future exploitation of such vulnerabilities.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.

More posts

Ameeba Chat