Freshworks FreshService Agent Scheduled Update Service cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Freshworks FreshService Agent. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component Scheduled Update Service. Such manipulation leads to cryptographic issue. This vulnerability is referenced as CVE-2022-36173. It is possible to launch the attack remotely. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Freshworks FreshService Agent (version now known). It has been rated as problematic. Affected by this issue is some unknown processing of the component Scheduled Update Service. The manipulation with an unknown input leads to a cryptographic issue vulnerability. Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality. CVE summarizes:
FreshService macOS Agent < 4.4.0 and FreshServce Linux Agent < 3.4.0 are vulnerable to TLS Man-in-The-Middle via the FreshAgent client and scheduled update service.
The weakness was published 09/13/2022. The advisory is shared for download at community.freshworks.com. This vulnerability is handled as CVE-2022-36173 since 07/18/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at community.freshworks.com.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
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: 🔍
Exploiting
Class: Cryptographic issueCWE: CWE-310
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: community.freshworks.com
Timeline
07/18/2022 🔍09/13/2022 🔍
09/13/2022 🔍
10/15/2022 🔍
Sources
Advisory: community.freshworks.comStatus: Confirmed
CVE: CVE-2022-36173 (🔍)
GCVE (CVE): GCVE-0-2022-36173
GCVE (VulDB): GCVE-100-208340
Entry
Created: 09/13/2022 10:10Updated: 10/15/2022 14:04
Changes: 09/13/2022 10:10 (39), 10/15/2022 14:04 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.