ProFTPD 1.2.9 Rc1 mod_sql_postgres User sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in ProFTPD 1.2.9 Rc1. This vulnerability affects unknown code of the component mod_sql_postgres. Performing a manipulation of the argument User results in sql injection. This vulnerability is identified as CVE-2003-0500. The attack can be initiated remotely. Additionally, an exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in ProFTPD 1.2.9 Rc1 (File Transfer Software). It has been classified as critical. This affects an unknown code of the component mod_sql_postgres. The manipulation of the argument USER with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in the PostgreSQL authentication module (mod_sql_postgres) for ProFTPD before 1.2.9rc1 allows remote attackers to execute arbitrary SQL and gain privileges by bypassing authentication or stealing passwords via the USER name.

The weakness was released 06/18/2003 by LINUX (Website). The advisory is shared at debian.org. This vulnerability is uniquely identified as CVE-2003-0500 since 06/30/2003. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 15175 (Debian DSA-338-1 : proftpd - SQL injection), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 27199 (ProFTPD SQL Injection mod_sql Vulnerability).

Upgrading to version 1.2.9rc1 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (12369), Exploit-DB (43), Tenable (15175), SecurityFocus (BID 7974†) and OSVDB (9507†). Entry connected to this vulnerability is available at VDB-112. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 15175
Nessus Name: Debian DSA-338-1 : proftpd - SQL injection
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 53627
OpenVAS Name: Debian Security Advisory DSA 338-1 (x-face-el)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: ProFTPD 1.2.9rc1

Timelineinfo

06/18/2003 🔍
06/19/2003 +1 days 🔍
06/19/2003 +0 days 🔍
06/29/2003 +10 days 🔍
06/30/2003 +1 days 🔍
08/07/2003 +38 days 🔍
08/18/2003 +11 days 🔍
04/09/2004 +234 days 🔍
09/29/2004 +173 days 🔍
08/14/2014 +3606 days 🔍
12/07/2024 +3768 days 🔍

Sourcesinfo

Advisory: debian.org
Researcher: LINUX
Status: Confirmed

CVE: CVE-2003-0500 (🔍)
GCVE (CVE): GCVE-0-2003-0500
GCVE (VulDB): GCVE-100-20661
X-Force: 12369
SecurityFocus: 7974 - ProFTPD SQL Injection mod_sql Vulnerability
OSVDB: 9507 - PostgreSQL Authentication Module (mod_sql) for ProFTPD USER Name Parameter SQL Injection
Vulnerability Center: 1685 - SQL Injection in the PostgreSQL Authentication Module, Critical

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 08/14/2014 18:31
Updated: 12/07/2024 21:48
Changes: 08/14/2014 18:31 (77), 05/11/2019 14:38 (9), 12/07/2024 21:48 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!