@oneuptime/common@10.0.24

The OneUptime Common UI Library is a collection of shared components, utilities that are used across the OneUptime platform. It is designed to be easy to install and use, and to be extensible. This library is built with React and TypeScript. It includes c

  • latest version

    12.0.10

  • latest non vulnerable version

  • first published

    2 years ago

  • latest version published

    6 hours ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the @oneuptime/common package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    SQL Injection

    @oneuptime/common is a The OneUptime Common UI Library is a collection of shared components, utilities that are used across the OneUptime platform. It is designed to be easy to install and use, and to be extensible. This library is built with React and TypeScript. It includes c

    Affected versions of this package are vulnerable to SQL Injection via the toSortStatement, toSelectStatement, and toGroupByStatement methods in StatementGenerator in the ClickHouse Identifier. An attacker can access, modify, or delete analytics data by injecting crafted input into the sort, select, or groupBy parameters of API requests.

    How to fix SQL Injection?

    Upgrade @oneuptime/common to version 10.0.34 or higher.

    <10.0.34
    • H
    Improper Verification of Cryptographic Signature

    @oneuptime/common is a The OneUptime Common UI Library is a collection of shared components, utilities that are used across the OneUptime platform. It is designed to be easy to install and use, and to be extensible. This library is built with React and TypeScript. It includes c

    Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in the WhatsApp POST webhook due to the improper verification of the Meta/WhatsApp X-Hub-Signature-256 HMAC signature. An attacker can manipulate notification delivery status records, suppress alerts, and corrupt audit trails by sending forged webhook payloads without authentication or signature verification.

    How to fix Improper Verification of Cryptographic Signature?

    Upgrade @oneuptime/common to version 10.0.34 or higher.

    >=10.0.23 <10.0.34