Austin Contract Computing Merchant Order Form 1.0/1.2 Shopping Cart information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Austin Contract Computing Merchant Order Form 1.0/1.2. This vulnerability affects unknown code of the component Shopping Cart. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-1999-0605. There is no exploit available.
Details
A vulnerability classified as problematic has been found in Austin Contract Computing Merchant Order Form 1.0/1.2. This affects an unknown functionality of the component Shopping Cart. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
An incorrect configuration of the Order Form 1.0 shopping cart CGI program could disclose private information.
The bug was discovered 04/20/1999. The weakness was shared 04/01/1999 as not defined posting (Bugtraq). The advisory is shared at marc.theaimsgroup.com. This vulnerability is uniquely identified as CVE-1999-0605. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
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 (3860), SecurityFocus (BID 2021†), OSVDB (6464†) and Vulnerability Center (SBV-9764†). The entries VDB-14590, VDB-14591, VDB-14592 and VDB-14593 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
ISS Proventia IPS: 🔍
Timeline
04/01/1999 🔍04/01/1999 🔍
04/20/1999 🔍
04/20/1999 🔍
11/29/2005 🔍
06/20/2014 🔍
04/19/2026 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
CVE: CVE-1999-0605 (🔍)
GCVE (CVE): GCVE-0-1999-0605
GCVE (VulDB): GCVE-100-14589
X-Force: 3860
SecurityFocus: 2021 - Merchant Order Form 1.2 Order Log Permissions Vulnerability
OSVDB: 6464 - CVE-1999-0605 - Merchant Order Form - Information Disclosure Issue
Vulnerability Center: 9764 - Merchant Order Form Discloses Costumers Credit Cards Numbers, Low
See also: 🔍
Entry
Created: 06/20/2014 23:16Updated: 04/19/2026 00:42
Changes: 06/20/2014 23:16 (57), 06/11/2019 20:45 (5), 04/19/2026 00:42 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.