| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GCOS-III on HIS 635 TS. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Fortran. This manipulation causes security check. No exploit exists.
Details
A vulnerability classified as critical was found in GCOS-III on HIS 635 TS (unknown version). Affected by this vulnerability is an unknown code block of the component Fortran. The manipulation with an unknown input leads to a security check vulnerability. The CWE definition for the vulnerability is CWE-358. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 10/01/1972 (Website). The advisory is shared at seclab.cs.ucdavis.edu. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1211 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 vulnerability database at OSVDB (22137†). The entry VDB-94898 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
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: 🔍
Exploiting
Class: Security checkCWE: CWE-358
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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: 🔍
Timeline
10/01/1972 🔍01/02/2006 🔍
01/02/2017 🔍
07/13/2020 🔍
Sources
Advisory: seclab.cs.ucdavis.eduStatus: Not defined
GCVE (VulDB): GCVE-100-94897
OSVDB: 22137 - GCOS-III on HIS 635 TS FORTRAN Assigned GO TO Envelope Bypass
See also: 🔍
Entry
Created: 01/02/2017 17:20Updated: 07/13/2020 14:25
Changes: 01/02/2017 17:20 (38), 07/13/2020 14:25 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.