References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

ChirpStack's SQLite-backend device tag filtering (chirpstack/src/storage/device.rs, in both get_count() and list()) interpolates the user-supplied tag KEY directly into a raw SQL fragment via Rust's format!() macro (`dsl::sql::<Bool>(&format!("device.tags->>'{}' =", k)).bind::<Text, _>(v)`), while only the tag VALUE is safely parameter-bound via Diesel's .bind(). An authenticated user with device-list access can inject SQL via a crafted tag key when the SQLite backend (chirpstack-sqlite package) is in use; the PostgreSQL backend is unaffected as it uses Diesel's native JSONB containment operator instead of raw SQL string formatting.

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE-89

https://github.com/chirpstack/chirpstack

https://github.com/chirpstack/chirpstack/blob/master/chirpstack/src/storage/device.rs

[{"vendor":"chirpstack","product":"chirpstack","defaultStatus":"unaffected","programFiles":["src/storage/device.rs"],"versions":[{"version":"0","lessThanOrEqual":"4.19.0-test.5","versionType":"semver","status":"affected"}]}]