Gw2Sharp

Gw2Sharp is a cross-platform .NET wrapper library for the official Guild Wars 2 API. Check the changelog at https://github.com/Archomeda/Gw2Sharp/blob/master/CHANGELOG.md

View on Nuget

Activity

Latest release: 3y ago
Total releases: 13
Cadence: ~2 months
Last 12 months: 0

Details

License: MIT
First release: Jan 01, 2021

Releases

Version	Released
`2.0.0-preview.1` pre	Mar 12, 2023
`1.7.4` patch	Feb 28, 2023
`1.7.3` patch	Jul 14, 2022
`1.7.2` patch	May 22, 2022
`1.7.1` patch	Apr 09, 2022
`1.7.0` minor	Feb 06, 2022
`1.6.1` minor	Dec 30, 2021
`1.5.0` minor	Nov 13, 2021
`1.4.0` minor	Sep 28, 2021
`1.3.0` minor	Sep 04, 2021
`1.2.0` minor	Jul 17, 2021
`1.1.0` minor	Apr 08, 2021
`1.0.0` initial	Jan 01, 2021

Dependencies (1)

Depends on

2.0.0-preview.1

Used by

Supply-chain exposure

1 tracked projects depend on this, <1% of every package we track.

A known CVE here directly exposes every one of them.

Known CVEs (1)

GHSA-4vr3-9v7h-5f8v Jun 18, 2019

Low severity vulnerability that affects Gw2Sharp

Low

Leaking cached authenticated requests

Impact

If you've been using one MemoryCacheMethod object in multiple instances of Gw2WebApiClient and are requesting authenticated endpoints with different access tokens, then you are likely to run into this bug.

When using an instance of MemoryCacheMethod and using it with multiple instances of Gw2WebApiClient, there's a possibility that cached authenticated responses are leaking to another request to the same endpoint, but with a different Guild Wars 2 access token. The latter request wouldn't start however, and would return the first cached response immediately. This means that the second response (or later responses) may contain the same data as the first response, therefore leaking data from another authenticated endpoint.

The occurence of this is limited however. The Guild Wars 2 API doesn't use the Expires header on most (if not all) authenticated endpoints. This header is checked when caching responses. If this header isn't available, the response isn't cached at all. You should still update to at least version 0.3.1 in order to be certain that it won't happen.

Patches

This bug has been fixed in version 0.3.1. When using an authenticated endpoint, it will prepend the SHA-1 hash of the access token to the cache id.

Workarounds

For version 0.3.0 and lower, you can use one separate instance of MemoryCacheMethod per Gw2WebApiClient if you need to use it.

For more information

If you have any questions or comments about this advisory, you can open an issue in the Gw2Sharp repository or contact me on Discord.

Affected versions

0.1.00.2.00.3.0

Fixed in

0.3.1

References

https://github.com/Archomeda/Gw2Sharp/security/advisories/GHSA-4vr3-9v7h-5f8v
https://github.com/Archomeda/Gw2Sharp
https://github.com/advisories/GHSA-4vr3-9v7h-5f8v

Updated Dec 02, 2024 · Source: OSV.dev

Insights

Releases per month

last 12 months

Release mix

minor 7
patch 4
pre 1

13 releases

Release calendar

2023

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Less More