106,837 results · Clear filters · Feed
-
Medium 6.1
OpenAM before 16.1.4 Open Redirect and XSS via goto and gotoOnFail
OpenAM before 16.1.4 contains an open redirect and cross-site scripting vulnerability that allows remote attackers to control post-login and logout destinations via the goto and gotoOnFail parameters. Attackers can craft OpenAM login or logout links that redi…
-
Medium 6.8
OpenAM before 16.1.4 Insufficient Response Validation in Internal SOAP Channel
OpenAM before 16.1.4 and its client SDK fail to sufficiently validate responses on the internal server-to-server SOAP channel, allowing network-positioned attackers to affect integrity and availability. Attackers who intercept unencrypted traffic or control a…
-
Medium 6.8
OpenAM before 16.1.4 PKCE Bypass in OAuth 2.0 Device Authorization Flow
OpenAM before 16.1.4 fails to enforce PKCE in the OAuth 2.0 device authorization flow, never validating the code verifier when device codes are exchanged for tokens. Attackers who obtain an approved device code from client logs or shared device storage can re…
-
Medium 4.7
OpenAM before 16.1.4 Open Redirect via SAML 1.x Trusted-Partner Matching
OpenAM before 16.1.4 contains an open redirect vulnerability that allows remote attackers to redirect users after SAML 1.x single sign-on by exploiting loose trusted-partner destination matching. Attackers can craft links to /SAMLAwareServlet or /SAMLPOSTProf…
-
Medium 4.8
OpenAM before 16.1.4 Stored XSS via OAuth 2.0 Consent Page Display Name
OpenAM before 16.1.4 contains a stored cross-site scripting vulnerability that allows privileged attackers to inject script by placing markup in a user's display name. When the victim reaches the OAuth 2.0 / OpenID Connect consent page, the unencoded name exe…
-
Medium 6.6
OpenAM before 16.1.4 SAML 1.x Signature Verification Issuer Impersonation
OpenAM before 16.1.4 does not verify that a signed SAML 1.x assertion or response was signed by the partner named as its issuer, accepting a signature from any certificate in OpenAM's keystore. An attacker holding such a private key, such as a trusted SAML 1.…
-
Medium 5.0
OpenAM before 16.1.4 SSRF via UMA Scope Description URLs
OpenAM before 16.1.4 contains a server-side request forgery vulnerability that allows parties registering UMA resource sets to trigger internal requests through unvalidated scope description URLs. Attackers can register resource sets with scope URLs pointing …
-
Medium 4.1
OpenAM before 16.1.4 SSRF via Federation Configuration Wizard Metadata URLs
OpenAM before 16.1.4 contains a server-side request forgery vulnerability that allows administrators, including delegated realm administrators, to make the server fetch arbitrary URLs through federation configuration wizard metadata URLs. Attackers can enter …
-
Medium 4.2
Tornado before 6.6 Cookie Attribute Injection via set_cookie max_age
Tornado before 6.6 does not validate the max_age argument of RequestHandler.set_cookie (also called by set_signed_cookie, set_secure_cookie, and clear_cookie), allowing injection of additional Set-Cookie attributes. When an application passes attacker-influen…
-
Medium 6.5
Tornado before 6.6 Path Traversal via static_url() Version Hashing
Tornado before 6.6 contains a path traversal vulnerability in RequestHandler.static_url() and get_version() that allows attackers to hash files outside static_path using ../ sequences. Attackers controlling input passed to static_url() can obtain SHA-512 hash…
-
Medium 5.5
Gitoxide before 0.42.0 Denial of Service via Crafted Commit-Graph File
gix-commitgraph before 0.42.0, as used in gitoxide before 0.61.0, contains a denial of service vulnerability because its commit-graph parser does not validate parent graph positions against the declared commit count or check the EDGE chunk length for 4-byte a…
-
Medium 6.5
gix-fs before 0.24.1 NTLM Credential Disclosure via Windows Symlink UNC Probe
gix-fs in gitoxide before 0.24.1 contains a credential disclosure vulnerability that allows remote attackers to capture NTLM credentials by supplying UNC symlink targets in a crafted repository. When a victim checks out the repository on Windows with symlinks…
-
Medium 5.9
Vikunja before 2.7.1 Missing Step-Up Authentication via TOTP Enrollment Endpoints
Vikunja before 2.7.1 contains a missing authentication vulnerability that allows attackers holding a stolen session to enroll and enable TOTP without the account password. Attackers can call the TOTP enroll and enable endpoints with their own secret to lock t…
-
Medium 4.6
Vikunja before 2.7.1 Stored CSS Injection via TipTap Table Cell data-background-color
Vikunja before 2.7.1 contains a stored CSS injection vulnerability that allows authenticated users with project write access to inject arbitrary CSS via unsanitized table-cell data-background-color attributes. Attackers can store crafted task descriptions or …
-
Medium 6.8
Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access tokens to keep authenticating because SetupTokenMiddleware skips session and account-status checks. Attackers with a stolen token can, after l…
-
Medium 5.4
Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass
Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delet…
-
Medium 5.4
Vikunja before 2.7.1 Mass Assignment via Team external_id Field
Vikunja before 2.7.1 contains a mass assignment vulnerability that allows any authenticated user to set the read-only external_id field through the team create and update endpoints. Attackers can tag a team they create or administer as externally managed, per…
-
Medium 6.5
Vikunja before 2.7.1 Memory Exhaustion DoS via Trello, Todoist and Microsoft To Do Migrations
Vikunja before 2.7.1 allocates memory without limits in its Trello, Todoist and Microsoft To Do migration importers, which buffer remote attachment downloads and API responses in memory without size caps. Authenticated users can start a migration that referen…
-
Medium 5.7
Vikunja 0.23.0 before 2.7.1 Information Disclosure via Webhook related_tasks Payload
Vikunja from 0.23.0 before 2.7.1 contains an information disclosure vulnerability that allows project collaborators with write access to read tasks from inaccessible projects by registering webhooks. Because webhook payloads are built with the triggering user…
-
Medium 6.5
Vikunja before 2.7.1 Memory Exhaustion via Unbounded Avatar Size Cache
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to exhaust server memory by requesting avatars at many distinct sizes. Attackers can upload a noisy avatar and fetch it at each size up to 1024, c…
-
Medium 5.9
Vikunja before 2.7.1 Password Brute-Force via TOTP Disable Endpoint
Vikunja before 2.7.1 contains an improper restriction of excessive authentication attempts vulnerability that allows session holders to brute-force account passwords via unthrottled re-authentication endpoints. Attackers with a stolen session can guess the pa…
-
Medium 6.5
Vikunja before 2.7.1 Memory Exhaustion DoS via WeKan and Vikunja-File Imports
Vikunja before 2.7.1 contains a denial of service vulnerability that allows authenticated users to exhaust API process memory by uploading WeKan or vikunja-file imports with no item-count cap. Attackers can submit a ~22 MB WeKan JSON with hundreds of thousand…
-
Medium 4.3
Vikunja before 2.7.1 Missing Authorization in Kanban Task-Bucket Move
Vikunja before 2.7.1 contains an incorrect authorization vulnerability in TaskBucket.CanUpdate, which checks write access to the bucket's project and to the task separately but never verifies that both belong to the same project. Authenticated users with writ…
-
Medium 4.3
Vikunja before 2.7.1 Information Disclosure via Team Self-Removal Endpoint
Vikunja before 2.7.1 contains an information disclosure vulnerability that allows authenticated users to determine whether private teams exist by calling the team member self-removal endpoint. Attackers can send DELETE requests to /teams/{id}/members/{own use…
-
Medium 4.3
Vikunja before 2.7.1 Resource Exhaustion via Vikunja-File ZIP Import
Vikunja before 2.7.1 contains a resource exhaustion vulnerability in the vikunja-file ZIP importer that allows authenticated users to consume CPU and memory by uploading archives with excessive entries. Attackers can upload export ZIPs containing many empty o…
-
Medium 4.1
Vikunja before 2.7.1 Client-Side Request Forgery via Stored Rich-Text Images
Vikunja before 2.7.1 contains a client-side request forgery vulnerability that allows users with write access to make viewers' clients request loopback or LAN addresses by storing img elements in rich text. Attackers can plant images in tasks, comments, proje…
-
Medium 4.3
Vikunja before 2.7.1 Orphaned Export Archives Enable Disk Exhaustion
Vikunja before 2.7.1 contains an improper resource cleanup vulnerability that leaves full-data export archives orphaned on disk after re-exports, failed exports, or account deletion. Authenticated users can repeatedly re-trigger exports containing all their a…
-
Medium 6.8
Vikunja before 2.7.1 Auth Token Leak via API URL Change
Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend API URL. Because checkAndSetApiUrl leaves origin-independent localStorage tokens in place, the bearer …
-
Medium 6.1
Vikunja before 2.7.1 Sensitive Token Exposure via URL Query in Access Logs
Vikunja before 2.7.1 embeds live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links, so the full request URI, including the token, is written to Vikunja's HTTP access log and any reverse-proxy logs when a u…
-
Medium 4.3
Vikunja before 2.7.1 Resource Exhaustion via CalDAV VTODO RELATED-TO Entries
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated CalDAV clients to create unbounded dummy tasks by sending VTODOs with thousands of RELATED-TO properties. Attackers can repeat unknown related UIDs in a…
-
Medium 4.3
Vikunja before 2.7.1 Denial of Service via Unbounded Kanban Bucket Count
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows project writers or view admins to create unlimited kanban buckets due to missing count caps. Attackers can create thousands of buckets so every kanban read runs a tas…
-
Medium 5.4
Vikunja 2.2.0 before 2.7.1 Token Scope Bypass via Project Webhook Endpoints
Vikunja from 2.2.0 before 2.7.1 contains an authorization bypass vulnerability that allows holders of tokens scoped only to projects_webhooks to manage the owner's user-level webhooks by supplying user_id in request bodies. Attackers can register user webhook…
-
Medium 5.5
Vikunja before 2.7.1 World-Readable Local File Storage and SQLite Database
Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read stored data because localStorage.Write creates blobs world-readable. Local attackers on a shared host can read attachments, project backgrounds and export…
-
Medium 4.3
Vikunja 0.22.0 before 2.7.1 Webhook URL Credential Exposure to Read-Only Members
Vikunja from 0.22.0 before 2.7.1 contains an information disclosure vulnerability that allows read-only project members to view full webhook target URLs by listing project webhooks. Attackers can extract incoming-webhook tokens or API keys embedded in target_…
-
Medium 5.4
Vikunja before 2.7.1 Improper Authorization in Kanban Bucket Deletion
Vikunja before 2.7.1 contains an improper authorization vulnerability in canDoBucket that allows users with project write access to delete buckets via a mismatched view ID. Attackers can request deletion through another view's bucket endpoint to bypass the la…
-
Medium 5.2
Vikunja before 2.7.1 Link-Share Hash Exposure via Request Path Logging
Vikunja before 2.7.1 contains an information exposure vulnerability that allows log readers to obtain link-share hashes because the request logger records the raw URI of the /shares/:share/auth route. Attackers with access to Vikunja or reverse proxy access l…
-
Medium 6.5
Vikunja before 2.7.1 Memory Exhaustion DoS via Unbounded Image Decodes
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to exhaust server memory through concurrent image decodes in avatar and background uploads. Attackers can send several parallel tiny, highly compr…
-
Medium 6.2
Vikunja before 2.7.1 Insecure Permissions on Dump Archive via vikunja dump
Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read dump archives created with umask permissions by the vikunja dump command. Local attackers on a shared host can read the world-readable zip in the rootpath…
-
Medium 5.9
Vikunja veans before 2.7.1 Credential Leak via Repo-Controlled .veans.yml Server
Vikunja veans before 2.7.1 contains a credential exposure vulnerability that allows malicious repository authors to capture API tokens by specifying an attacker-controlled server in .veans.yml. When veans runs in an untrusted checkout, it sends VEANS_TOKEN as…
-
Medium 6.8
Vikunja veans before 2.7.1 HTTPS to HTTP Downgrade in Server Discovery
Vikunja veans before 2.7.1 contains a protocol downgrade vulnerability in serverCandidates that allows on-path attackers to force plain HTTP during veans init and login. Attackers can block HTTPS ports so discovery accepts an unverified HTTP response, capturi…