Merge pull request #116 from 0xn3va/develop

Fix new lines inside tables

Author: 0xn3va

Container/Escaping/cve-list.md

@@ -2,9 +2,9 @@
 
 | CVE | Title | Affected versions | References |
 | --- | --- | --- | --- |
-| [CVE-2021-30465](https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r) | mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs | <=1.0.0-rc94 | <p>[Github advisories: GHSA-c3xm-pvg7-gh7r](https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r)</p><p>[runc mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs (CVE-2021-30465)](http://blog.champtar.fr/runc-symlink-CVE-2021-30465/)</p> |
+| [CVE-2021-30465](https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r) | mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs | <=1.0.0-rc94 | <p>> [Github advisories: GHSA-c3xm-pvg7-gh7r](https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r)</p><p>> [runc mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs (CVE-2021-30465)](http://blog.champtar.fr/runc-symlink-CVE-2021-30465/)</p> |
 | [CVE-2019-19921](https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw) | procfs race condition with a shared volume mount | <1.0.0-rc10 | [Github advisories: GHSA-fh74-hm69-rqjw](https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw) |
-| [CVE-2019-5736](https://nvd.nist.gov/vuln/detail/CVE-2019-5736) | Overwrite host runc binary due to file-descriptor mishandling | <=1.0-rc6 | <p>[CVE-2019-5736: Escape from Docker and Kubernetes containers to root on host](https://blog.dragonsector.pl/2019/02/cve-2019-5736-escape-from-docker-and.html)</p><p>[Breaking out of Docker via runC – Explaining CVE-2019-5736](https://unit42.paloaltonetworks.com/breaking-docker-via-runc-explaining-cve-2019-5736/)</p> |
+| [CVE-2019-5736](https://nvd.nist.gov/vuln/detail/CVE-2019-5736) | Overwrite host runc binary due to file-descriptor mishandling | <=1.0-rc6 | <p>> [CVE-2019-5736: Escape from Docker and Kubernetes containers to root on host](https://blog.dragonsector.pl/2019/02/cve-2019-5736-escape-from-docker-and.html)</p><p>> [Breaking out of Docker via runC – Explaining CVE-2019-5736](https://unit42.paloaltonetworks.com/breaking-docker-via-runc-explaining-cve-2019-5736/)</p> |
 
 # Containerd
 
@@ -14,7 +14,7 @@
 | [CVE-2021-32760](https://github.com/containerd/containerd/security/advisories/GHSA-c72p-9xmj-rx3w) | Archive package allows chmod of file outside of unpack target directory | <p><=1.4.7</p><p><=1.5.3</p> | [Github advisories: GHSA-c72p-9xmj-rx3w](https://github.com/containerd/containerd/security/advisories/GHSA-c72p-9xmj-rx3w) |
 | [CVE-2021-21334](https://github.com/containerd/containerd/security/advisories/GHSA-6g2q-w5j3-fwh4) | containerd CRI plugin: environment variables can leak between containers | <p><=1.3.9</p><p><= 1.4.3</p> | [Github advisories: GHSA-6g2q-w5j3-fwh4](https://github.com/containerd/containerd/security/advisories/GHSA-6g2q-w5j3-fwh4) |
 | [CVE-2020-15257](https://research.nccgroup.com/2020/11/30/technical-advisory-containerd-containerd-shim-api-exposed-to-host-network-containers-cve-2020-15257/) | containerd-shim API Exposed to Host Network Containers | <p><=1.3.7</p><p>1.4.0</p><p>1.4.1</p> | [Technical Advisory: containerd – containerd-shim API Exposed to Host Network Containers (CVE-2020-15257)](https://research.nccgroup.com/2020/11/30/technical-advisory-containerd-containerd-shim-api-exposed-to-host-network-containers-cve-2020-15257/) |
-| [CVE-2020-15157](https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c) | containerd v1.2.x can be coerced into leaking credentials during image pull | < 1.3.0 | <p>[Github advisories: GHSA-742w-89gc-8m9c](https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c)</p><p>[CVE-2020-15157 "ContainerDrip" Write-up](https://darkbit.io/blog/cve-2020-15157-containerdrip)</p> |
+| [CVE-2020-15157](https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c) | containerd v1.2.x can be coerced into leaking credentials during image pull | < 1.3.0 | <p>> [Github advisories: GHSA-742w-89gc-8m9c](https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c)</p><p>> [CVE-2020-15157 "ContainerDrip" Write-up](https://darkbit.io/blog/cve-2020-15157-containerdrip)</p> |
 
 # Linux kernel
 

Mobile Application/Android/Overview/app-data-files.md

@@ -5,7 +5,7 @@ Android uses a file system that's similar to disk-based file systems on other pl
 - **Databases** - storage for structured data in a private database using the Room persistence library.
 
 |  | Type of content | Access method | Permissions needed |
-|: --- |: --- |: --- |: --- |
+| --- | --- | --- | --- |
 | [App-specific files](https://developer.android.com/training/data-storage/app-specific) | App-specific files | <p>From internal storage, [getFilesDir()](https://developer.android.com/reference/android/content/Context#getFilesDir%28%29) and [getCacheDir()](https://developer.android.com/reference/android/content/Context#getCacheDir%28%29)</p><p>From external storage, [getExternalFilesDir()](https://developer.android.com/reference/android/content/Context#getExternalFilesDir%28java.lang.String%29) and [getExternalCacheDir()](https://developer.android.com/reference/android/content/Context#getExternalCacheDir%28%29)</p> | <p>Never needed for internal storage</p><p>Not needed for external storage when your app is used on devices that run Android 4.4 (API level 19) or higher</p> |
 | [Media](https://developer.android.com/training/data-storage/shared/media) | Shareable media files (images, audio files, videos) | [MediaStore](https://developer.android.com/reference/android/provider/MediaStore) API | <p>**READ_EXTERNAL_STORAGE** when accessing other apps' files on Android 11 (API level 30) or higher</p><p>**READ_EXTERNAL_STORAGE** or **WRITE_EXTERNAL_STORAGE** when accessing other apps' files on Android 10 (API level 29)</p><p>Permissions are required for all files on Android 9 (API level 28) or lower</p> |
 | [Documents and other files](https://developer.android.com/training/data-storage/shared/documents-files) | Other types of shareable content, including downloaded files | Storage Access Framework | None |

Mobile Application/Android/Overview/app-package.md

@@ -7,7 +7,7 @@ Android apps are distributed in APK (Android package) archives. The APK file is
 The APK file has the following structure:
 
 | Name | Type | Description |
-|: --- |: --- :|: --- |
+| --- | --- | --- |
 | META-INF | Directory | This directory contains APK metadata. |
 | META-INF/MANIFEST.MF | File | This file contains various information used by the Java run-time environment when loading the JAR file, such as which is the main class to be run, version of a package, build number, creator of the package, security policies/permissions of Java applets and Java webstart packages, the list of file names in the JAR along with their SHA-256 digests, etc. |
 | META-INF/CERT.RSA or META-INF/CERT.DSA | File | Contains signed content of `CERT.RF` and is used to verify app integrity with the public key. |

Mobile Application/iOS/Overview/app-data-files.md

@@ -9,7 +9,7 @@ For security purposes, an iOS app's interactions with the file system are limite
 Bundle directory consists of all the files that come along with the application when installed from Apple's App Store or any other source. Much important information can be obtained about the application from the files in these directories. The main components of the Bundle directory of a native iOS application:
 
 | Name | Type | Description |
-|: --- |: --- :|: --- |
+| --- | --- | --- |
 | _CodeSignature | Directory | This directory contains the CodeResources file, which is used to store the signature of all files in the bundle that are signed. |
 | Application Binary | File | This file contains the application's executable code. The name of this file is the same as that of the name of the .app directory excluding the extension '.app'. |
 | Application Icon | File | These are the icon files of the application. There are multiple icon files (MyAppIcon.png, [email protected] etc.) for representation of the application on devices with different resolution like iPhone or iPad. |
@@ -51,7 +51,7 @@ Data container or Local Data Storage container is used to store data locally for
 Commonly used directories of the data container:
 
 | Name | Description |
-|: --- |: --- |
+| --- | --- |
 | Documents | <p>This directory is used to store user-generated content. The contents of this directory can be accessed by the user through file sharing; therefore, this directory should only contain files that can be made available to the user.</p><p>The contents of this directory are backed up by iTunes and iCloud.</p> |
 | Documents/Inbox | <p>This directory is used to access files that the app was asked to open by outside entities. Specifically, the Mail program places email attachments associated with app in this directory. Document interaction controllers may also place files in it.</p><p>The app can read and delete files in this directory but cannot create new files or write to existing files.</p><p>The contents of this directory are backed up by iTunes and iCloud.</p> |
 | Library | <p>This is the top-level directory for any files that are not user data files.</p><p>**Application Support**. This directory is used to store all app data files except those associated with the user's documents. Sometimes it may also be used to store a modifiable copy of resources contained initially in the app's bundle.</p><p>**Caches**. This directory is used to write any app-specific support files that the application can recreate easily. The data in this directory is mostly the cache for the analytics that can be sent when required and also the server’s responses for delivering quick responses to the user’s queries.This directory also stores the screenshot of the application in the Snapshots directory when it moves to the background in order to improve user experience.</p><p>**Preferences**. This directory contains app-specific preference files. The main file in this directory is the file named .plist which is used by the developers to store information using NSUserDefaults class.</p><p>The contents of the Library directory (with the exception of the Caches subdirectory) are backed up by iTunes and iCloud.</p> |

Mobile Application/iOS/Overview/app-package.md

@@ -3,7 +3,7 @@ iOS apps are distributed in IPA (iOS App Store Package) archives. The IPA file i
 At a high level, the IPA file has the following structure:
 
 | Name | Type | Description |
-|: --- |: --- :|: --- |
+| --- | --- | --- |
 | Payload | Directory | This directory contains all the application data. |
 | Payload/MyApp.app | Directory | [Bundle directory](/Mobile%20Application/iOS/Overview/app-data-files.md#bundle-container-structure). |
 | Payload/MyApp.app/MyApp | File | This file contains the application's executable code |

Mobile Application/iOS/Overview/deployment.md

@@ -79,7 +79,7 @@ Example of ad hoc profile plist file:
 The provisioning profile consists of several items, the most important of which are described below.
 
 | Item | Description |
-|: --- :|: --- |
+| --- | --- |
 | App ID | An App ID is a two-part string (`29QTLV4HFP.com.mycompany.myapp`: alpha-numeric characters and App Bundle ID) used to identify one or more apps from a single development team (this can include a `*` wild card to be used for many applications with similar bundle identifiers). |
 | <p>Development Certificates | Development Certificate is a unique security certificate issued by Apple that uniquely identifies you as the developer or publisher of the application. The private key of the distribution certificate is used to sign the application. There are two types of signing certificates:</p><p>**Development certificate** is used for individual developers who are actively debugging and developing an application.</p><p>**Production certificate** is used either a production setting (final build for the App Store) or a QA build that is distributed through Apple's TestFlight Beta or another app test distribution system. These certificates identify you as an App Store Publisher to Apple or as a Test Distributor and can only be used with production provisioning profiles.</p> |
 | Unique Device Identifiers | List of device IDs on which the application can run on. |