eGain Web Email API 11+ Message /system/ws/v11/ss/email fromName/message Header Injection input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in eGain Web Email API 11+. This affects an unknown function of the file /system/ws/v11/ss/email of the component Message Handler. Performing a manipulation of the argument fromName/message with the input %0a/%0d as part of Parameter results in input validation (Header Injection).
This vulnerability is reported as CVE-2019-17123. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in eGain Web Email API 11+ (Automation Software) (affected version not known). This affects some unknown functionality of the file /system/ws/v11/ss/email of the component Message Handler. The manipulation of the argument fromName/message with the input value %0a/%0d leads to a input validation vulnerability (Header Injection). CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The eGain Web Email API 11+ allows spoofed messages because the fromName and message fields (to /system/ws/v11/ss/email) are mishandled, as demonstrated by fromName header injection with a %0a or %0d character. (Also, the message parameter can have initial HTML comment characters.)
The weakness was disclosed 12/13/2019. This vulnerability is uniquely identified as CVE-2019-17123 since 10/04/2019. 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 are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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
Name: Header InjectionClass: Input validation / Header Injection
CWE: CWE-20
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: 🔍
Timeline
10/04/2019 🔍12/13/2019 🔍
12/14/2019 🔍
03/12/2024 🔍
Sources
Advisory: egain.comStatus: Not defined
CVE: CVE-2019-17123 (🔍)
GCVE (CVE): GCVE-0-2019-17123
GCVE (VulDB): GCVE-100-147177
Entry
Created: 12/14/2019 14:57Updated: 03/12/2024 07:34
Changes: 12/14/2019 14:57 (39), 12/14/2019 15:02 (18), 03/12/2024 07:34 (3)
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.