Skip to content
Fencer Intel
medium —

GHSA-gpv5-rp6w-58r8 json

Remote code execution vulnerability in dependency System.Drawing.Common

published 3y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

The core Akka module depended on an old System.Configuration.ConfigurationManager version 4.7.0 which transitively depends on System.Common.Drawing v4.7.0. The System.Common.Drawing v4.7.0 is affected by a remote code execution vulnerability https://github.com/advisories/GHSA-ghhp-997w-qr28.

The real-world impact of this should be low, but users should be advised to upgrade to later versions of Akka.NET.

### Patches _Has the problem been patched? What versions should users upgrade to?_

This issue is resolved in Akka.NET v1.4.46 and Akka.NET v1.5.0-alpha3.

### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_

You might be able to explicitly reference System.Configuration.ConfigurationManager's NuGet package and upgrade to 6.0.1 or later without upgrading Akka.NET, but it's probably best to upgrade Akka.NET itself.

### References _Are there any links users can visit to find out more?_

Original issue: https://github.com/akkadotnet/akka.net/issues/6226 MSFT advisory: https://github.com/advisories/GHSA-ghhp-997w-qr28

### For more information If you have any questions or comments about this advisory:

* Open an issue in [the Akka.NET repository](https://github.com/akkadotnet/akka.net/issues/new) * Contact us on [the Akka.NET Discord](https://discord.gg/GSCfPwhbWP)

Patch / fix

  • nuget Akka 1.4.46, 1.5.0-alpha3

Is GHSA-gpv5-rp6w-58r8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
nuget Akka
<1.4.46
>=1.5.0-alpha1, <1.5.0-alpha3
1.4.46
1.5.0-alpha3

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.