How many CVEs have patched setTo?

2 published CVEs changed setTo in alkacon/opencms-core, in 1 distinct patches totalling 4 changed lines, between 2006 and 2006.

What is the latest CVE that changed setTo?

CVE-2006-3934 (Alkacon OpenCMS Absolute Path Traversal via pathname in filePath parameter), published 2006-07-31, changed lines 238 of src-modules/org/opencms/workplace/tools/workplace/broadcast/CmsMessageInfo.java.

How does setTo compare to the rest of alkacon/opencms-core?

alkacon/opencms-core has 17 CVEs with a located fix in total; 2 of them changed setTo.

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

alkacon/opencms-core

Function

setTo

Name: setTo in alkacon/opencms-core: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src-modules/org/opencms/workplace/tools/workplace/broadcast/CmsMessageInfo.java

Last patched July 31, 2006

2

CVEs

That changed this function

1

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2006

Years

By CVE publication date

Overview

setTo in alkacon/opencms-core was changed by 2 published CVE fixes in 2006, in 1 distinct patches that added or removed 4 lines in total.

alkacon/opencms-core has 17 CVEs with a located fix in total, so 12% of them touched this function.

CVEs that patched it

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

Alkacon OpenCMS Absolute Path Traversal via pathname in filePath parameter
CVE-2006-3934 · line 238 · +1 −1
Medium · CVSS 4.6
EPSS 1.5%2006-07-31
Alkacon OpenCMS Improper Access Control via system/workplace/views/admin/admin-main.jsp
CVE-2006-3935 · line 238 · +1 −1
Medium · CVSS 6.2
EPSS 1.8%2006-07-31

Get an alert when the next CVE fix lands in alkacon/opencms-core, with the patched functions.

Monitor opencms-core CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1checkStringsrc-modules/org/opencms/workplace/tools/workplace/broadcast/CmsMessageInfo.java3 CVEs · 2 patches2006

Other hotspots in the repository

Functions in alkacon/opencms-core changed by the most CVE fixes.

checkString3 CVEs · src-modules/org/opencms/workplace/tools/workplace/broadcast/CmsMessageInfo.java printError2 CVEs · src/org/opencms/workplace/explorer/CmsTree.java initWorkplaceRequestValues2 CVEs · src/org/opencms/workplace/explorer/CmsTree.java getRootPath2 CVEs · src/org/opencms/util/CmsRfsFileViewer.java generateXml2 CVEs · src/org/opencms/configuration/CmsWorkplaceConfiguration.java CmsRfsFileViewer2 CVEs · src/org/opencms/util/CmsRfsFileViewer.java

All patched functions in alkacon/opencms-core

Frequently asked questions

Common questions about CVE fixes to setTo.

How many CVEs have patched setTo?: 2 published CVEs changed setTo in alkacon/opencms-core, in 1 distinct patches totalling 4 changed lines, between 2006 and 2006.
What is the latest CVE that changed setTo?: CVE-2006-3934 (Alkacon OpenCMS Absolute Path Traversal via pathname in filePath parameter), published 2006-07-31, changed lines 238 of src-modules/org/opencms/workplace/tools/workplace/broadcast/CmsMessageInfo.java.
How does setTo compare to the rest of alkacon/opencms-core?: alkacon/opencms-core has 17 CVEs with a located fix in total; 2 of them changed setTo.
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 alkacon/opencms-core 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