SendCard 3.3.0 Error Message sendcard.php sc_language information disclosure
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. |
---|---|---|
5.1 | $0-$5k | 0.00 |
A vulnerability was found in SendCard 3.3.0. It has been rated as problematic. Affected by this issue is an unknown part of the file sendcard.php of the component Error Message Handler. The manipulation of the argument sc_language
with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. Impacted is confidentiality. CVE summarizes:
SendCard 3.3.0 allows remote attackers to obtain sensitive information via an invalid sc_language parameter to sendcard.php, which reveals the path in an error message.
The weakness was shared 05/31/2007 as not defined posting (Bugtraq). The advisory is shared for download at securityfocus.com. This vulnerability is handled as CVE-2007-3059 since 06/05/2007. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a exploit are known.
After before and not just, there has been an exploit disclosed. It is declared as highly functional.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (34672) and Secunia (SA25085). The entries 36582, 36581 and 37150 are related to this item.
Product
Name
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200
ATT&CK: Unknown
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Threat: 🔍Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/02/2007 🔍05/31/2007 🔍
05/31/2007 🔍
06/05/2007 🔍
06/05/2007 🔍
03/15/2015 🔍
09/03/2018 🔍
Sources
Advisory: securityfocus.comStatus: Not defined
CVE: CVE-2007-3059 (🔍)
Secunia: 25085
X-Force: 34672 - Sendcard sendcard.php sc_language information disclosure
OSVDB: 35740 - sendcard sendcard.php sc_language Variable Path Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/15/2015 03:58 PMUpdated: 09/03/2018 08:17 AM
Changes: (1) source_secunia
Complete: 🔍
Comments
Might our Artificial Intelligence support you?
Check our Alexa App!
No comments yet. Please log in to comment.