vim is vulnerable to Heap-based Buffer Overflow

Permalink

Browse files

patch 8.2.3669: buffer overflow with long help argument

Problem:    Buffer overflow with long help argument.
Solution:   Use snprintf().

*   Loading branch information

![@brammool](https://avatars.githubusercontent.com/u/8530623?s=40&v=4)

1 parent bb277fd commit bd228fd097b41a798f90944b5d1245eddd484142

Showing with **12 additions** and **2 deletions**.

1.  +1 −2 src/help.c
2.  +9 −0 src/testdir/test\_help.vim
3.  +2 −0 src/version.c

@@ -422,8 +422,7 @@ find\_help\_tags(

|| (vim\_strchr((char\_u \*)"%\_z@", arg\[1\]) != NULL

&& arg\[2\] != NUL)))

{

STRCPY(d, "/\\\\\\\\");

STRCPY(d + 3, arg + 1);

vim\_snprintf((char \*)d, IOSIZE, "/\\\\\\\\%s", arg + 1);

// Check for "/\\\\\_$", should be "/\\\\\_\\$"

if (d\[3\] == '\_' && d\[4\] == '$')

STRCPY(d + 4, "\\\\$");

@@ -134,4 +134,13 @@ func Test\_help\_window\_height()

close

endfunc

  

func Test\_help\_long\_argument()

try

exe 'help \\%' .. repeat('0', 1021)

catch

call assert\_match("E149:", v:exception)

endtry

endfunc

  

  

" vim: shiftwidth\=2 sts\=2 expandtab

@@ -757,6 +757,8 @@ static char \*(features\[\]) =

  

static int included\_patches\[\] =

{ /\* Add new patch number below this line \*/

/\*\*/

3669,

/\*\*/

3668,

/\*\*/

**0 comments on commit `bd228fd`**

Please sign in to comment.

CVE-2021-4019: patch 8.2.3669: buffer overflow with long help argument · vim/vim@bd228fd

Insufficient Input Validation in Web Applications operating on Business-DNA Solutions GmbH’s TopEase® Platform Version <= 7.1.27 allows an authenticated remote attacker with Object Modification privileges to insert arbitrary HTML without code execution.

CVE-2021-42117: Release Notes - TopEase Documentation

An insufficient session expiration vulnerability exists in Business-DNA Solutions GmbH’s TopEase® Platform Version <= 7.1.27, which allows a remote attacker to reuse, spoof, or steal other user and admin sessions.

CVE-2021-42545: Release Notes - TopEase Documentation

An unauthenticated SQL Injection vulnerability in Rosario Student Information System (aka rosariosis) before 8.1.1 allows remote attackers to execute PostgreSQL statements (e.g., SELECT, INSERT, UPDATE, and DELETE) through /Side.php via the syear parameter.

**Description**

Unauthenticated SQL Injection vulnerability in Rosario Student Information System version 8.1 allows remote attackers to execute PostgreSQL statements (e.g.: SELECT, INSERT, UPDATE, DELETE) through _**/Side.php**_ via _**syear**_ parameter.

This vulnerability is a result of two issues:

*   **OWASP Top 10:2021 - A01:2021 – Broken Access Control**
*   **OWASP Top 10:2021 - A03:2021 – Injection**

**Plugin**

**README**

Vulnerability Type:

SQL Injection (SQLi)

Vendor of the product(s):

RosarioSIS

Affected product(s)/code base:

8.1

Has vendor confirmed or acknowledged the vulnerability:

Yes

Attack type:

Unauthenticated

Impact & Description:

C:H/I:H/A:H

Affected Component:

/Side.php, /Warehouse.php, /functions/Current.php, /functions/GetMP.php

Attack vector(s):

Remote

Proof of concept (PoC):

Details below

References:

Issue #328 (closed)

Severity:

Critical (9.8)

CVSS v3.1 Vector String:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

**Initial Communication**

Hi @francoisjacquet,

Found two issues in the latest version of RosarioSIS (version 8.1).

Many thanks & hope this helps!

– IJ

**Environment Details**

*   **RosarioSIS 8.1**
*   **PHP 7.4.21**
*   **PostgreSQL 13.3**

**Proof-of-Concept**

The following command can be used to replicate this finding

    sqlmap -u "http://hostname/path/Side.php" --data="sidefunc=update&syear=111" --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36" --delay=0 --timeout=30 --retries=0 -p "syear" --dbms="PostgreSQL" --technique BET --level=5 --risk=3 --threads=1 --time-sec=5 -b --current-user --current-db --dbs --answers="crack=N,dict=N,continue=Y,quit=N" -v 0 --drop-set-cookie --flush-session

![image](https://gitlab.com/uploads/855eff680e104d100ff7cd7fea4fde64/image.png)

**Recommendations******OWASP Top 10:2021 - A01:2021 – Broken Access Control****

*   Create a session handler which will be imported on all PHP files of RosarioSIS
*   Always check if the current session is authenticated or not & handle execution flow accordingly
*   Avoid exposing conditional statements which directly accept user-supplied input
*   Wrap code with intended functionality within declared functions
*   Prevent unauthenticated users from directly supplying input & controlling execution flow

****OWASP Top 10:2021 - A03:2021 – Injection****

*   Do not trust user-supplied input, always perform validation at the back-end / server-side
*   Create a whitelist at the back-end to filter out malicious characters from user-supplied input
    *   Example: When expecting string input (e.g.: First Name, Last Name) from the user
        *   Filter against \[a-zA-Z0-9\]\* (and some symbols if necessary - @, ., etc)
        *   Drop or ignore all else - dangerous characters from user-supplied input (e.g.: <, >, , ', ", \`, $, %, !, ?, -, +, \_, #, \[, \], (, ), etc)
*   Ensure proper data type handling is observed
    *   Example: When expecting an integer (e.g.: sYear) from the user
        *   Accept string input -> Sanitize input -> Check if input is valid integer -> SQL query
*   For SQL, make use of parameterized queries, prepared statements & stored procedures after sanitizing user-supplied input

**References**

*   https://owasp.org/Top10/A01\_2021-Broken\_Access\_Control/
*   https://owasp.org/Top10/A07\_2021-Identification\_and\_Authentication\_Failures/
*   https://owasp.org/Top10/A03\_2021-Injection/
*   https://stackoverflow.com/questions/60174/how-can-i-prevent-sql-injection-in-php
*   https://stackoverflow.com/questions/4712037/what-is-parameterized-query
*   https://www.php.net/manual/en/pdo.prepared-statements.php
*   https://security.stackexchange.com/questions/32334/what-dangerous-characters-need-to-be-filtered-from-user-input-prior-to-use-in-a

**Analysis**

During the analysis, breakpoints were set in Visual Studio Code for the following files

*   At _**/Side.php**_ on the following lines:
    *   10, 25, 56, 59, 452
*   At _**functions/GetMP.php**_ on the following line:
    *   406

**A01:2021 – Broken Access Control**

The file _**/Side.php**_ (and other php files in RosarioSIS) does not implement access controls or session management checks to prevent any unauthenticated user from executing its code by directly accessing it through a browser.

Since no session management checks are implemented, visiting _**/Side.php**_ through a browser causes _**lines 85 - 90**_ of _**/Warehouse.php**_ to be executed from _**line 10**_ of _**/Side.php**_ - which is a code snippet that loads php files within the _**functions/**_ directory of the web server:

_**Lines 1 - 19 of /Side.php (emphasis on line 10)**_

         1  <?php
         2  /**
         3   * Side
         4   *
         5   * Side menu
         6   *
         7   * @package RosarioSIS
         8   */
         9
        10  require_once 'Warehouse.php';
        11
        12  $old_school = UserSchool();
        13  $old_syear = UserSyear();
        14  $old_period = UserCoursePeriod();
        15
        16  $unset_student = $unset_staff = $update_body = false;
        17
        18  $addJavascripts = '';
        19

_**Lines 82 - 90 of /Warehouse.php**_

        82  /**
        83   * Load functions
        84   */
        85  $functions = glob( 'functions/*.php' );
        86
        87  foreach ( $functions as $function )
        88  {
        89          require_once $function;
        90  }

_**Import of _functions/GetMP.php_ from _/Side.php_**_

![image](https://gitlab.com/uploads/c16af81f08958786a9bedcdada8700c0/image.png)

Since the conditional _**if statement**_ on _**lines 25 - 30**_ _(boxed in red below)_ checks for user-controlled parameters ($\_REQUEST, $\_POST), an unauthenticated user could craft & supply a request which will pass the conditional check and ultimately control the application's execution flow.

![image](https://gitlab.com/uploads/d886006c8c0055a41f5921f03198ff3f/image.png)

This can be done by sending a request that:

*   Contains a parameter "sidefunc=update"
*   Is an HTTP POST request

    POST /rosariosis-v8.1/Side.php HTTP/1.1
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36
    Host: 192.168.254.140
    Connection: close
    Content-Type: application/x-www-form-urlencoded
    Content-Length: 117
    
    
    sidefunc=update&syear=111'+OR+(SELECT(SELECT+CASE+WHEN+(SUBSTRING('poc',2,1)=CHR(ASCII('o')))+THEN+1+ELSE+0+END)=1)--

After passing the first conditional check, another series of conditional _**if statements**_ beginning at _**line 35**_ (pointed with a red arrow in the image above) will be executed.

However, since the condition in _**line 35**_ is not met, execution will continue to the following _**else if statement**_ at _**line 53**_ which leads to the SQL Injection vulnerability.

![image](https://gitlab.com/uploads/578a6b593f07ea5055975e4fae1586c0/image.png)

**A03:2021 – Injection**

The value of HTTP POST parameter _**syear**_ is assigned to the HTTP SESSION parameter _**UserSyear**_ at _**line 56**_ which is then passed on to _**line 59**_ where the _**GetCurrentMP()**_ function is called with the _**DBDate()**_ argument.

![image](https://gitlab.com/uploads/380b67f92f7a4bee3d692f835b2dab9c/image.png)

![image](https://gitlab.com/uploads/e75147233e86864878f0a1ea8ebcd15c/image.png)

Stepping into from _**line 59**_ leads to the function definition of _**DBDate()**_ at _**line 32**_ of _**functions/Date.php**_ which returns the current date in ISO format (e.g. 2021-09-25). This value is passed on to GetCurrentMP() as its 2nd argument.

![image](https://gitlab.com/uploads/c8b94652b0ca67ded1c51afa558d0417/image.png)

Stepping into from _**line 32**_ of _**functions/Date.php**_ leads to the function definition of _**GetCurrentMP()**_ which starts at _**line 404**_ of _**functions/GetMP.php**_

![image](https://gitlab.com/uploads/3575b52356eb97655e677b37234da249/image.png)

A SQL query is defined in _**lines 411 - 416**_ where it is assigning to the SQL query parameter _**SYEAR**_ the returned value of the function call to _**UserSyear()**_

![image](https://gitlab.com/uploads/580c7a50cf15b64b52eecbf440812465/image.png)

Stepping into from _**line 411**_ of _**functions/GetMP.php**_ leads to the function definition of _**UserSyear()**_ located in _**line 27**_ of _**functions/Current.php**_ which shows that its returning the value initially assigned to the HTTP POST request parameter _**syear**_ which was assigned earlier.

![image](https://gitlab.com/uploads/147059e256bce26268dbec8302ff6af3/image.png)

From this point, the SQL query is executed through the _**DBQuery()**_ function which is defined in _**database.inc.php**_. The output can be observed at the postgresql log file (If logging is enabled). This can lead to a Time-based blind SQL Injection attack.

![image](https://gitlab.com/uploads/a0d15baaf3fc13b76acc1979b1d79f34/image.png)

![image](https://gitlab.com/uploads/acb8e24cc75233cd67c4fcb6b21bc53d/image.png)

It was also observed that the injected SQL query is being executed again on _**line 452**_ of _**Side.php**_ - The error message & injected SQL query is actually displayed from Side.php which can also lead to Error-based & Boolean-based blind SQL Injection attacks.

![image](https://gitlab.com/uploads/6f8f85f8b4f07037806dda772d315204/image.png)

![image](https://gitlab.com/uploads/12d41d3c6191f3a16cf1d52c03afd138/image.png)

CVE-2021-44427: Improper Access Control leading to Unauthenticated SQL Injection (#328) · Issues · François Jacquet / rosariosis

An improper authentication vulnerability has been reported to affect QNAP device, VioStor. If exploited, this vulnerability allows attackers to compromise the security of the system.
We have already fixed this vulnerability in the following versions of QVR:
QVR FW 5.1.6 build 20211109 and later


<< Back to Security Advisory List

*   **Release date:** November 26, 2021
*   **Security ID:** QSA-21-52
*   **Severity:** High
*   **CVE identifier:** CVE-2021-38686
*   **Affected products:** QNAP VS Series NVR
*   **Status:** Resolved

**Summary**

An improper authentication vulnerability has been reported to affect QNAP VS Series NVR running QVR. If exploited, this vulnerability allows attackers to compromise the security of the system.

We have already fixed the vulnerability in the following versions of QVR:

*   QVR 5.1.6 build 20211109 and later

**Recommendation**

To secure your device, we strongly recommend updating your system to the latest version to benefit from vulnerability fixes.

**Updating QVR**

1.  Log on to QVR as administrator.
2.  Go to **Control Panel** > **System Settings** > **Firmware Update**.
3.  Select the **Firmware Update** tab.
4.  Click **Browse...** to upload the latest firmware file.  
    **Tip:** Download the latest firmware file for your specific device from https://www.qnapsecurity.com/n/en/product\_x\_down/.
5.  Click **Update System**.  
    QVR installs the updates.

**Acknowledgements:** JPCERT/CC

**Revision History:** V1.0 (November 26, 2021) - Published

CVE-2021-38686: Improper Authentication Vulnerability in QVR - Security Advisory

A command injection vulnerability has been reported to affect QNAP device, VioStor. If exploited, this vulnerability allows remote attackers to run arbitrary commands.
We have already fixed this vulnerability in the following versions of QVR:
QVR FW 5.1.6 build 20211109 and later


<< Back to Security Advisory List

*   **Release date:** November 26, 2021
*   **Security ID:** QSA-21-51
*   **Severity:** Critical
*   **CVE identifier:** CVE-2021-38685
*   **Affected products:** QNAP VS Series NVR
*   **Status:** Resolved

**Summary**

A command injection vulnerability has been reported to affect QNAP VS Series NVR running QVR. If exploited, this vulnerability allows remote attackers to run arbitrary commands.

We have already fixed the vulnerability in the following versions of QVR:

*   QVR 5.1.6 build 20211109 and later

**Recommendation**

To secure your device, we strongly recommend updating your system to the latest version to benefit from vulnerability fixes.

**Updating QVR**

1.  Log on to QVR as administrator.
2.  Go to **Control Panel** > **System Settings** > **Firmware Update**.
3.  Select the **Firmware Update** tab.
4.  Click **Browse...** to upload the latest firmware file.  
    **Tip:** Download the latest firmware file for your specific device from https://www.qnapsecurity.com/n/en/product\_x\_down/.
5.  Click **Update System**.  
    QVR installs the update.

**Acknowledgements:** JPCERT/CC

**Revision History:** V1.0 (November 26, 2021) - Published

CVE-2021-38685: Command Injection Vulnerability in QVR - Security Advisory

Cross-site scripting vulnerability in Booking Package - Appointment Booking Calendar System versions prior to 1.5.11 allows a remote attacker to inject an arbitrary script via unspecified vectors.

CVE-2021-20840: Booking Package – Appointment Booking Calendar System

Microsoft Edge for iOS Spoofing Vulnerability

CVE-2021-43220

Buffer Overflow vulnerability in tvnviewer.exe of TightVNC Viewer allows a remote attacker to execute arbitrary instructions via a crafted FramebufferUpdate packet from a VNC server.

CVE-2021-42785: TightVNC: What's New in TightVNC

A Reflected Cross-Site Scripting vulnerability in McAfee Policy Auditor prior to 6.5.2 allows a remote unauthenticated attacker to inject arbitrary web script or HTML via the UID request parameter. The malicious script is reflected unmodified into the Policy Auditor web-based interface which could lead to the extract of end user session token or login credentials. These may be used to access additional security-critical applications or conduct arbitrary cross-domain requests.

**First Published:** November 22, 2021

**Product:**

**Impacted Versions:**

**CVE ID:**

**Impact of Vulnerabilities:**

**Severity Ratings:**

**CVSS v3.1  
Base/Temporal Scores:**

Policy Auditor

Prior to 6.5.2

CVE-2021-31851

CWE-79:  Improper Neutralization of Input During Web Page Generation (‘Cross-Site Scripting’)

Medium

6.1 / 5.5

Policy Auditor

Prior to 6.5.2

CVE-2021-31852

CWE-79:  Improper Neutralization of Input During Web Page Generation (‘Cross-Site Scripting’) 

Medium

6.1 / 5.5

 **Recommendations:**

Install or update to the Policy Auditor 6.5.2 November 2021 release.

 **Security Bulletin Replacement:**

None

 **Location of updated software:**

Product Downloads site

To receive email notification when this Security Bulletin is updated, click **Subscribe** on the right side of the page. You must be logged on to subscribe.

**Article contents:**

*   Vulnerability Description
*   Remediation
*   Frequently Asked Questions (FAQs)
*   Resources
*   Disclaimer

**Vulnerability Description**  
The Policy Auditor web-based user interface incorrectly sanitized web script or HTML in the profileNodeID and UIDs response parameters allowing an attacker to obtain session token or login credentials and conduct arbitrary cross-domain requests. Access to the user interface is expected to be restricted to the local network, meaning an attacker would need to be on your network.

1.  **CVE-2021-31851**  
    A Reflected Cross-Site Scripting vulnerability in McAfee Policy Auditor prior to 6.5.2 allows a remote unauthenticated attacker to inject arbitrary web script or HTML via the profileNodeID request parameters. The malicious script is reflected unmodified into the Policy Auditor web-based interface which could lead to the extraction of end user session token or login credentials. These may be used to access additional security-critical applications or conduct arbitrary cross-domain requests.  
    NVD CVE-2021-31851  
    MITRE CVE-2021-31851  
     
2.  **CVE-2021-31852**  
    A Reflected Cross-Site Scripting vulnerability in McAfee Policy Auditor prior to 6.5.2 allows a remote unauthenticated attacker to inject arbitrary web script or HTML via the UID request parameter. The malicious script is reflected unmodified into the Policy Auditor web-based interface which could lead to the extract of end user session token or login credentials. These may be used to access additional security-critical applications or conduct arbitrary cross-domain requests.  
    NVD CVE-2021-31852  
    MITRE CVE-2021-31852

**Remediation**  
To remediate this issue, customers should install or update to the Policy Auditor 6.5.2 November 2021 release.

Go to the Product Downloads site, and download the applicable product update file:

**Product**

**Version**

**Type**

**Release Date**

Policy Auditor

6.5.2

Update

November 22, 2021

 

**Download and Installation Instructions**  
For instructions to download product updates and hotfixes, see: KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.  
**Frequently Asked Questions (FAQs)**  
**How do I know if my product is vulnerable or not?**

For endpoint products:

Use the following instructions for endpoint or client-based products:

1.  Right-click the McAfee tray shield icon on the Windows taskbar.
2.  Select **Open Console**.
3.  In the console, select **Action Menu**.
4.  In the Action Menu, select **Product Details**. The product version displays.

**What is CVSS?**  
Common Vulnerability Scoring System (CVSS) is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.

  When calculating CVSS scores, McAfee Enterprise has adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We don’t factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.

  **What are the CVSS scoring metrics?**

1.  **CVE-2021-31851: Cross-Site Scripting vulnerability in Policy Auditor**  
     
    
    **Base Score**
    
    **6.1**
    
    Attack Vector (AV)
    
    Network (N)
    
    Attack Complexity (AC)
    
    Low (L)
    
    Privileges Required (PR)
    
    None (N)
    
    User Interaction (UI)
    
    Required (R)
    
    Scope (S)
    
    Changed (C)
    
    Confidentiality (C)
    
    Low (L)
    
    Integrity (I)
    
    Low (L)
    
    Availability (A)
    
    None (N)
    
    **Temporal Score (Overall)**
    
    **5.5**
    
    Exploitability (E)
    
    Proof-of-Concept (P)
    
    Remediation Level (RL)
    
    Official Fix (O)
    
    Report Confidence (RC)
    
    Confirmed (C)
    
       
    **NOTE:** This CVSS version 3.1 vector was used to generate this score.  
     
2.  **CVE-2021-31852:** **Cross-Site Scripting vulnerability in Policy Auditor**  
     
    
    **Base Score**
    
    **6.1**
    
    Attack Vector (AV)
    
    Network (N)
    
    Attack Complexity (AC)
    
    Low (L)
    
    Privileges Required (PR)
    
    None (N)
    
    User Interaction (UI)
    
    Required (R)
    
    Scope (S)
    
    Changed (C)
    
    Confidentiality (C)
    
    Low (L)
    
    Integrity (I)
    
    Low (L)
    
    Availability (A)
    
    None (N)
    
    **Temporal Score (Overall)**
    
    **5.5**
    
    Exploitability (E)
    
    Proof-of-Concept (P)
    
    Remediation Level (RL)
    
    Official Fix (O)
    
    Report Confidence (RC)
    
    Confirmed (C)
    
       
    **NOTE:** This CVSS version 3.1 vector was used to generate this score.

**Where can I find a list of all Security Bulletins?**  
All Security Bulletins are published on our external PSIRT website. To see Security Bulletins for McAfee Enterprise products on this website, click **Enterprise Security Bulletins**. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).

  **How do I report a product vulnerability to McAfee Enterprise?**  
If you have information about a security issue or vulnerability with a McAfee Enterprise product, go to the PSIRT website, click **Report a Security Vulnerability**, and follow the instructions.

  **How does McAfee Enterprise respond to this and any other reported security flaws?**  
Our key priority is the security of our customers. If a vulnerability is found within any McAfee Enterprise software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.

  McAfee Enterprise only publishes Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.

  View our PSIRT policy on the PSIRT website by clicking **About PSIRT**.  
**Resources**

Para ponerse en contacto con el Soporte técnico, inicie sesión en ServicePortal y vaya a Crear una solicitud de servicio en https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:

*   Si está registrado, introduzca su ID de usuario y contraseña y, a continuación, haga clic en **Iniciar sesión**.
*   Si no está registrado, haga clic en **Registrarse** y rellene los campos obligatorios. Recibirá por correo electrónico la contraseña y las instrucciones para iniciar sesión.

**Disclaimer**  
The information provided in this Security Bulletin is provided as is without warranty of any kind. McAfee Enterprise disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee Enterprise or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if McAfee Enterprise or its suppliers have been advised of the possibility of such damages. Some states don’t allow the exclusion or limitation of liability for consequential or incidental damages so the preceding limitation may not apply.

  Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn’t be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren’t a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion and may be changed or canceled at any time.

Tag

#ios