22
33## Supported Versions
44
5- The following versions of open62541 are monitored for vulnerabilities and are part of our vulnerability handling and release process.
5+ The open62541 releases are organized into release families. The following table
6+ shows the current nomenclature concerning development and stable release
7+ families.
68
7- | Version | Community Support | Commercial Support Available |
8- | --------- | ------------------- | ---------------------------- |
9- | master | :heavy_check_mark : | :heavy_check_mark : |
10- | v1.4.x | :heavy_check_mark : | :heavy_check_mark : |
11- | v1.3.x | :last_quarter_moon : | :heavy_check_mark : |
12- | <= v1.2.x | :last_quarter_moon : | :heavy_check_mark : |
13- | <= v1.0.x | :x : | :last_quarter_moon : |
9+ | Release Family | Status | Branch |
10+ | -------------- | ------------------- | ----------- |
11+ | - | development | master |
12+ | v1.5.x | stable | 1.5 |
13+ | v1.4.x | oldstable | 1.4 |
14+ | v1.3.x | oldoldstable | 1.3 |
1415
15- ## Reporting a Vulnerability
16+ Beyond the public Github, you can get professional support for open62541 from
17+ * o6 Automation GmbH* (https://www.o6-automation.com/services ). This includes our
18+ ** Vulnerability Management Process** and ** Long-Term Support** for older stable
19+ release families. So software based on open62541 can be deployed and supported
20+ in the field for many years.
1621
17- Security vulnerabilities can be disclosed privately to the mailing list open62541-security@googlegroups.com .
22+ ## Reporting a Vulnerability
1823
19- The disclosure triggers an evaluation of the vulnerability.
20- Depending on the criticality, the follow-up comprises of the following steps:
24+ You are invited to disclose your findings privately with one of the following
25+ mechanisms. ** DO NOT OPEN PUBLIC GITHUB ISSUES FOR POTENTIAL VULNERABILITIES.**
26+ This only gives the bad guys a head-start and does not speed up the
27+ vulnerability handling.
2128
22- - Responsible disclosure of the vulnerability to critical professional users (with an embargo period)
23- - Commit of the fix to the public repository
24- - Backporting of the fix to past release families
25- - Preparation of patch releases
26- - Public disclosure of the vulnerability
29+ - Via email to the mailing list open62541-security@googlegroups.com
30+ - Via the Github disclosure mechanism at https://github.com/open62541/open62541/security/advisories
2731
28- You can send us encrypted email with PGP using this public key:
32+ You can encrypt emails to us with this PGP key:
2933
3034```
3135-----BEGIN PGP PUBLIC KEY BLOCK-----
@@ -43,3 +47,29 @@ tfp1v8HATMXKB65FmujmBg==
4347=Juz6
4448-----END PGP PUBLIC KEY BLOCK-----
4549```
50+
51+ ## Vulnerability Management Process
52+
53+ The disclosure of a potential vulnerability triggers our Vulnerability
54+ Management Process. It comprises of the following steps:
55+
56+ 1 . Evaluation of the disclosure (CVSS score)
57+ 2 . If relevant, preparation of mitigations (patches) for the impacted open62541
58+ release families together with a non-public Vulnerability Advisory
59+ 3 . Dissemination to commercial users and operators of critical infrastructure
60+ 4 . Embargo time (typically 30 days)
61+ 5 . Merge of the mitigations into the impacted open62541 release family branches
62+ 6 . Preparation of open62541 patch releases for the impacted release families
63+
64+ ## Acknowledgement and Public CVE
65+
66+ ** We do not endorse public CVE advisories for open62541.** With todays AI-based
67+ coding tools, a public CVE has roughly the same impact as releasing a working
68+ exploit. Professional users and operators of critical installations receive
69+ non-public Vulnerability Advisories via the Professional Support Services. Then,
70+ after an embargo time to fix critical installations, we prepare public patch
71+ releases for the impacted versions of open62541.
72+
73+ If the person disclosing a vulnerability wishes so, we can give a personal
74+ acknowledgement of the disclosure both in the non-public Vulnerability Advisory
75+ and in the commits that are eventually merged into the public git branches.
0 commit comments