Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain a cross-site request forgery (CSRF) vulnerability in the Special:SMWAdmin page. This vulnerability allows an attacker to trick an authenticated smw-admin user into performing unintended actions such as schema setup, entity disposal, or job execution. Exploitation can result in semantic data loss and resource exhaustion.
Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 contain a vulnerability that allows anonymous attackers to cause excessive resource consumption. By sending repeated requests to the Special:PropertyLabelSimilarity page with a limit parameter set to zero, attackers can bypass SQL limits and trigger quadratic computations. This leads to exhaustion of PHP CPU, memory, and database connections, resulting in a denial of service condition.
Semantic MediaWiki versions from 7.3.0 up to but not including 7.3.1 have a missing authorization vulnerability in the smwtask update task. This flaw allows users with edit rights to force semantic updates on arbitrary pages, potentially causing resource-intensive operations and unauthorized semantic-store writes.
SemanticMediaWiki versions from 3.0.0 up to but not including 7.3.1 contain a reflected cross-site scripting (XSS) vulnerability in the Special:Ask feature. This flaw arises because certain separator parameters are output without proper HTML escaping in various result printers. Unauthenticated attackers can exploit this by crafting malicious Special:Ask links that execute JavaScript in the context of the wiki, potentially stealing session cookies or CSRF tokens.
Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain an uncontrolled recursion vulnerability in the LegacyParser::getSubqueryDescription() function. This flaw allows unauthenticated attackers to submit deeply nested query elements to the action=ask API, causing excessive CPU and memory consumption that can tie up server request workers. The vulnerability leads to a denial-of-service condition by exhausting server resources.
Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 have an improper authorization vulnerability. This flaw allows ordinary editors to add an 'Is edit protected' annotation, which causes indefinite edit and move restrictions to be applied without verifying the author's rights. As a result, other editors and administrators can be locked out of editing or moving pages permanently.
Octopus Server versions prior to a specified fix perform OIDC token issuer validation inconsistently. This flaw allows tokens from improperly configured non-legitimate issuers to be accepted as valid service account tokens from trusted issuers. Exploitation requires a service account with an OIDC identity configured and knowledge or guessing of identity details. The vulnerability has a high severity rating with a CVSS score of 8.7.
A heap-based buffer overflow vulnerability exists in JP1/Base versions from 11-00 up to but not including 12-50-54. This vulnerability allows an attacker to execute arbitrary code or cause a denial of service due to memory corruption.
Semantic MediaWiki versions from 7.3.0 up to but not including 7.3.1 contain a missing authorization vulnerability in the smwtask API module. This flaw allows unauthenticated attackers to run queued jobs and force store updates. Exploitation can involve using the public anonymous CSRF token with the run-joblist function to execute arbitrary job types repeatedly or invoking updates on sysop-protected pages, potentially leaking page titles and exhausting system resources.
A critical stack-based buffer overflow vulnerability exists in multiple JP1 products, including JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager and Agent editions, and JP1/Base. The affected versions range from 13-00 up to but not including 13-50-31 for most products, and from 11-00 up to but not including 12-50-54 for JP1/Base. This vulnerability allows for remote exploitation without privileges or user interaction, potentially leading to high confidentiality and integrity impact with limited availability impact.
An out-of-bounds write vulnerability exists in multiple JP1 products, including JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager and Agent editions, and JP1/Base. The affected versions are prior to specific fixed releases. This vulnerability has a critical severity with a CVSS score of 9.4, indicating high impact on confidentiality, integrity, and availability.
A stack-based buffer overflow vulnerability exists in the web management interface of certain Moxa wireless device servers. An authenticated remote attacker with low privileges can exploit insufficient bounds checking on user input to cause the web management service to become unresponsive. Recovery requires power cycling the device, though other device functions continue to operate normally.
A heap-based buffer overflow vulnerability exists in multiple JP1 products, including JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager and Agent editions, and JP1/Base. The affected versions range from 13-00 up to but not including 13-50-31 for the first four products, and from 11-00 up to but not including 12-50-54 for JP1/Base. This vulnerability has a high CVSS score of 9.4, indicating critical severity with potential for high impact on confidentiality and integrity.
SemanticMediaWiki versions from 3.1.0 up to but not including 7.3.1 contain a reflected cross-site scripting (XSS) vulnerability. This flaw allows unauthenticated attackers to inject malicious scripts via the unescaped default parameter in JsonResultPrinter. Exploitation involves tricking users into visiting a specially crafted Special:Ask link with a zero-result query and a specific request_type, leading to execution of JavaScript in the context of the wiki. This can result in theft of session cookies or CSRF tokens.
Semantic MediaWiki versions from 2.5.0 up to but not including 7.3.1 contain an uncontrolled resource consumption vulnerability. This flaw allows low-privilege editors to bypass the smwgMaxNumRecurringEvents limit by supplying a large limit parameter. Attackers can exploit this by saving pages with #set_recurring_event without specifying an end date, causing the creation of thousands or millions of date subobjects. This results in exhaustion of CPU, memory, and database resources, leading to denial of service conditions.
Semantic MediaWiki versions from 3.0.0 up to but not including 7.3.1 contain an algorithmic complexity vulnerability in the TermParser::normalize_compact_form() function. This flaw allows unauthenticated attackers to cause quadratic CPU consumption by submitting long search terms with many distinct in:(...) or has:(...) expressions to Special:Search when the extended search engine is enabled. This can exhaust PHP search workers, leading to denial of service conditions.
A critical stack-based buffer overflow vulnerability exists in HiRDB Server versions 9 and 10 within specified version ranges. The flaw allows for remote exploitation without privileges or user interaction, potentially leading to high confidentiality and integrity impact, and low availability impact.
A heap-based buffer overflow vulnerability exists in JP1/Automatic Job Management System 3 - Manager versions from 10-00 up to but not including 13-50-31. This vulnerability has a critical severity with a CVSS score of 9.4, indicating it can be exploited remotely without privileges or user interaction, potentially leading to high confidentiality and integrity impact and some availability impact.
A heap-based buffer overflow vulnerability exists in JP1/Automatic Job Management System 3 affecting Manager and Agent components from version 11-00 up to but not including 13-50-31. This vulnerability has a critical CVSS score of 9.8, indicating it can be exploited remotely without privileges or user interaction to cause high impact on confidentiality, integrity, and availability.
A heap-based buffer overflow vulnerability exists in HiRDB Server versions 9 and 10, affecting multiple sub-versions. This flaw allows an attacker to execute arbitrary code or cause a denial of service due to memory corruption. The vulnerability has a critical severity with a CVSS score of 9.8.