CVE-2022-4768

CRITICALNVD 6.39.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-12-28. NVD baseline CVSS 6.3; sources differ by 3.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability was found in Dropbox merou. It has been classified as critical. Affected is the function add_public_key of the file grouper/public_key.py of the component SSH Public Key Handler. The manipulation of the argument public_key_str leads to injection. It is possible to launch the attack remotely. The name of the patch is d93087973afa26bc0a2d0a5eb5c0fde748bdd107. It is recommended to apply a patch to fix this issue. VDB-216906 is the identifier assigned to this vulnerability.

CVSS v3
6.3
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Oct 13, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
GitHub pull request

Block injection attack in ssh public key handling

Fix merged in dropbox/merou PR #673 on 2022-03-28 — awaiting tagged release

https://github.com/dropbox/merou/pull/673
GitHub commit

commit d93087973afa (dropbox/merou)

Fix landed in dropbox/merou commit d93087973afa — awaiting tagged release

https://github.com/dropbox/merou/commit/d93087973afa26bc0a2d0a5eb5c0fde748bdd107

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 18:04 UTCEG score recompute
  2. 2026-10-13 18:04 UTCGHSA enrichmentGHSA-r4w8-5mfm-rhh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-12 17:50 UTCEG score recompute
  5. 2026-10-12 17:50 UTCGHSA enrichmentGHSA-r4w8-5mfm-rhh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-11 22:06 UTCEG score recompute
  8. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-09-30 16:11 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  19. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-09-24 02:06 UTCOSV refresh
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 63 more
  1. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  7. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  8. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  9. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  10. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  11. 2026-09-04 19:54 UTCOSV refresh
  12. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  14. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  15. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  17. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  18. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  19. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  26. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  27. 2026-08-18 07:04 UTCOSV refresh
  28. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  29. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  30. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  31. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  32. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  33. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  34. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  35. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  36. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  37. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  38. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  39. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  40. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  41. 2026-08-03 01:57 UTCOSV refresh
  42. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  43. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  44. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  45. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  46. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  47. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  48. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  49. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  50. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  51. 2026-07-23 02:15 UTCEG score recompute
  52. 2026-07-22 23:03 UTCEG score recompute
  53. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  54. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  55. 2026-07-20 17:05 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  56. 2026-07-19 14:29 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  57. 2026-07-19 02:27 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  58. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  59. 2026-07-16 17:00 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  60. 2026-07-16 11:19 UTCOSV refresh
  61. 2026-07-15 16:56 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  62. 2026-07-15 01:58 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  63. 2026-07-13 22:28 UTCEPSS rescoreEPSS 0.7% · 47th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-4768?
CVE-2022-4768 is a critical-severity vulnerability; its CVE record was published on December 27, 2022. A vulnerability was found in Dropbox merou. It has been classified as critical. Affected is the function addpublickey of the file grouper/publickey.py of the component SSH Public Key Handler. The manipulation of the argument publickey_str leads to injection. It is possible to launch the attack…
When was the CVE record for CVE-2022-4768 published?
The CVE record for CVE-2022-4768 was published on December 27, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-4768 actively exploited?
CVE-2022-4768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-4768?
CVE-2022-4768 has a CVSS v3 base score of 6.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-4768?
An upstream fix for CVE-2022-4768 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-4768

Explore →

Is Your Infrastructure Affected by CVE-2022-4768?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs