Approved changes feed: RSS · Atom

cpe:2.3:a:gentoo:soko:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorGentoo (7fa277de-5a05-5db1-a5d1-2f4db074c494)
ProductSoko (223eeefb-9f95-5e22-ac1b-8d7ed0f038fd)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/gentoo/soko purl2cpe 2026-06-01 10:12:48.540490
pkg:golang/github.com/gentoo/soko purl2cpe 2026-06-01 10:12:48.540493

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-28424 vulnerable 2026-06-03 14:51:09.195214 Soko SQL Injection vulnerability
CRITICAL (9.1)
Soko if the code that powers packages.gentoo.org. Prior to version 1.0.2, the two package search handlers, `Search` and `SearchFeed`, implemented in `pkg/app/handler/packages/search.go`, are affected by a SQL injection via the `q` parameter. As a result, unauthenticated attackers can execute arbitrary SQL queries on `https://packages.gentoo.org/`. It was also demonstrated that primitive was enough to gain code execution in the context of the PostgreSQL container. The issue was addressed in commit `4fa6e4b619c0362728955b6ec56eab0e0cbf1e23y` of version 1.0.2 using prepared statements to interpolate user-controlled data in SQL queries.
Published: 2023-03-20T12:47:13.250Z
Updated: 2025-02-25T14:52:46.552Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-26033 vulnerable 2026-06-03 14:50:57.355477 Gentoo soko contains DoS attack based on SQL Injection
HIGH (7.5)
Gentoo soko is the code that powers packages.gentoo.org. Versions prior to 1.0.1 are vulnerable to SQL Injection, leading to a Denial of Service. If the user selects (in user preferences) the "Recently Visited Packages" view for the index page, the value of the `search_history` cookie is used as a base64 encoded comma separated list of atoms. These are string loaded directly into the SQL query with `atom = '%s'` format string. As a result, any user can modify the browser's cookie value and inject most SQL queries. A proof of concept malformed cookie was generated that wiped the database or changed it's content. On the database, only public data is stored, so there is no confidentiality issues to site users. If it is known that the database was modified, a full restoration of data is possible by performing a full database wipe and performing full update of all components. This issue is patched with commit id 5ae9ca83b73. Version 1.0.1 contains the patch. If users are unable to upgrade immediately, the following workarounds may be applied: (1.) Use a proxy to always drop the `search_history` cookie until upgraded. The impact on user experience is low. (2.) Sanitize to the value of `search_history` cookie after base64 decoding it.
Published: 2023-02-24T23:29:36.567Z
Updated: 2025-03-10T21:06:03.363Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.