How many CVEs have patched checkPublicKeyValidity?

1 published CVEs changed checkPublicKeyValidity in nextcloud/desktop, in 2 distinct patches totalling 26 changed lines, between 2021 and 2021.

What is the latest CVE that changed checkPublicKeyValidity?

CVE-2021-32728 (End-to-end encryption device setup did not verify public key), published 2021-08-18, changed lines 805 to 830 of src/libsync/clientsideencryption.cpp.

How does checkPublicKeyValidity compare to the rest of nextcloud/desktop?

nextcloud/desktop has 14 CVEs with a located fix in total; 1 of them changed checkPublicKeyValidity.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

nextcloud/desktop

Function

checkPublicKeyValidity

Name: checkPublicKeyValidity in nextcloud/desktop: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/libsync/clientsideencryption.cpp

Last patched August 18, 2021

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

26

Lines changed

Added plus removed

2021

Years

By CVE publication date

Overview

checkPublicKeyValidity in nextcloud/desktop was changed by 1 published CVE fixes in 2021, in 2 distinct patches that added or removed 26 lines in total.

nextcloud/desktop has 14 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed checkPublicKeyValidity, newest first, with the lines each fix touched.

End-to-end encryption device setup did not verify public key
CVE-2021-32728 · lines 805–830 · +26 −0
Medium · CVSS 6.5
EPSS 0.9%2021-08-18

Get an alert when the next CVE fix lands in nextcloud/desktop, with the patched functions.

Monitor desktop CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in nextcloud/desktop changed by the most CVE fixes.

slotFolderEncryptedMetadataReceived3 CVEs · src/libsync/propagateuploadencrypted.cpp metadataReceived2 CVEs · src/libsync/discoveryphase.cpp generateCSR2 CVEs · src/libsync/clientsideencryption.cpp encryptedMetadata2 CVEs · src/libsync/clientsideencryption.cpp setupExistingMetadata2 CVEs · src/libsync/clientsideencryption.cpp editFileLocally2 CVEs · src/gui/folderman.cpp

All patched functions in nextcloud/desktop

Frequently asked questions

Common questions about CVE fixes to checkPublicKeyValidity.

How many CVEs have patched checkPublicKeyValidity?: 1 published CVEs changed checkPublicKeyValidity in nextcloud/desktop, in 2 distinct patches totalling 26 changed lines, between 2021 and 2021.
What is the latest CVE that changed checkPublicKeyValidity?: CVE-2021-32728 (End-to-end encryption device setup did not verify public key), published 2021-08-18, changed lines 805 to 830 of src/libsync/clientsideencryption.cpp.
How does checkPublicKeyValidity compare to the rest of nextcloud/desktop?: nextcloud/desktop has 14 CVEs with a located fix in total; 1 of them changed checkPublicKeyValidity.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track nextcloud/desktop CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing