Static Web Server
Approved changes feed: RSS · Atom
cpe:2.3:a:static-web-server:static_web_server:*:*:*:*:*:rust:*:*part: a version: * update: *
| Vendor | Static Web Server (25328e07-59d9-53ab-aa31-aa48ffe42283) |
|---|---|
| Product | Static Web Server (10b50a58-9917-5490-85bd-dbc06f9d07ab) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | rust |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/static-web-server/static-web-server |
purl2cpe | 2026-06-01 10:11:06.255500 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-27480 |
vulnerable | 2026-06-08 07:53:22.364394 |
Static Web Server: Timing-Based Username Enumeration in Basic Authentication
MEDIUM (5.3)
Static Web Server (SWS) is a production-ready web server suitable for static web files or assets. In versions 2.1.0 through 2.40.1, a timing-based username enumeration vulnerability in Basic Authentication allows attackers to identify valid users by exploiting early responses for invalid usernames, enabling targeted brute-force or credential-stuffing attacks. SWS checks whether a username exists before verifying the password, causing valid usernames to follow a slower code path (e.g., bcrypt hashing) while invalid usernames receive an immediate 401 response. This timing discrepancy allows attackers to enumerate valid accounts by measuring response-time differences. This issue has been fixed in version 2.41.0.
Published: 2026-02-21T09:14:30.376Z
Updated: 2026-02-24T18:13:51.921Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-67487 |
vulnerable | 2026-06-08 07:41:19.885457 |
Static Web Server is vulnerable to symbolic link Path Traversal
Static Web Server (SWS) is a production-ready web server suitable for static web files or assets. Versions 2.40.0 and below contain symbolic links (symlinks) which can be used to access files or directories outside the intended web root folder. SWS generally does not prevent symlinks from escaping the web server’s root directory. Therefore, if a malicious actor gains access to the web server’s root directory, they could create symlinks to access other files outside the designated web root folder either by URL or via the directory listing. This issue is fixed in version 2.40.1.
Published: 2025-12-09T03:35:58.257Z
Updated: 2025-12-09T16:02:20.028Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.