External risk intelligence

St. Joe ERP SQL Injection via Login Endpoint

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2024-13979

The vulnerability exists in the login endpoint of an ERP system. ERP login portals are designed to be internet-facing to facilitate remote access for users. Because the flaw is reachable via unauthenticated HTTP POST requests to this login page, the vulnerable surface is public-facing by design and commonly accessible over the internet.

SQL Injection

St Joe Erp System Project St Joe Erp System

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical security flaw has been identified in the St. Joe ERP system, allowing attackers to potentially access or alter sensitive company data through unauthorized database commands. This vulnerability exists in the system's login function and does not require any authentication to exploit.

  • Flaw lets unauthenticated attackers misuse the system's login.
  • Unfettered database access could compromise sensitive information.
  • Confirm if this ERP system is in use and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can reach the St. Joe ERP system's login page from anywhere on the internet and send specially crafted HTTP POST requests. The system processes this input without properly sanitizing it, allowing the attacker to inject malicious SQL commands into database queries. This can lead to unauthorized access to or modification of sensitive data within the ERP system.

  • Unauthenticated remote access required.
  • Crafted HTTP POST to login endpoint.
  • Unauthorized data access and service disruption.

Live Threat

Current exploitation, exposure, and threat context

This SQL injection vulnerability in the St. Joe ERP system's login endpoint could allow unauthenticated attackers to manipulate the backend database, potentially leading to unauthorized access or modification of records when exploited.

  • Sensitive business data could be exposed.
  • Attackers could send crafted POST requests.
  • Unauthorized data access or modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

The St. Joe ERP system's SQL injection vulnerability likely falls under the responsibility of application owners and infrastructure teams. The immediate priority is to locate all instances of this ERP system, determine their exposure and criticality, and identify the accountable owner for each deployment to initiate a risk-based remediation plan.

  • Identify ERP system instances and owners.
  • Verify external reachability and business impact.
  • Plan coordinated remediation or mitigation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the St. Joe ERP system and why is it used?

St. Joe ERP (Enterprise Resource Planning) is a software platform designed to manage and automate core business processes such as finance, operations, supply chain, and human resources. Organizations use it to centralize data, helping them track resources and improve administrative efficiency across the entire company.

What is the vulnerability class for CVE-2024-13979?

This issue is classified as CWE-89, known as SQL Injection. It occurs when an application takes untrusted user input and embeds it directly into a database query without proper validation or sanitization. In this case, the flaw allows an attacker to manipulate the backend database by sending malicious SQL commands through the software's login screen.

How does an attacker trigger this vulnerability?

An attacker triggers the vulnerability by sending a specially crafted HTTP POST request to the system's login endpoint. Because the application fails to scrub this input before processing it, the database executes the attacker's unintended commands. Normal interactions with the login page that do not include malicious code do not trigger this vulnerability.

Is my instance of the St. Joe ERP system at risk?

The risk is elevated because the vulnerability exists at the login portal, which is typically exposed to the internet. According to the Halo Surface Signal analysis, this ERP component is often intentionally public-facing to support remote user access. If your installation is reachable over the internet, it is considered directly exposed to potential unauthenticated attacks.

What steps should I take if I use St. Joe ERP?

First, locate all running instances of the software and identify the internal teams responsible for them. Assess whether these instances are accessible from the internet and prioritize securing any public-facing logins. Work with your IT or application owners to verify if a patch or configuration change is available to resolve the underlying input sanitization issue.

References