CVE-2018-17090

CVE 描述

An issue was discovered in DonLinkage 6.6.8. The modules /pages/bazy/bazy_adresow.php and /pages/proxy/add.php are vulnerable to stored XSS that can be triggered by closing

followed by <script></script> tags.                            </div>
                        </div>

<div class="table-responsive">
                <table class="table table-striped gy-7 gs-7">
                    <thead>
                    <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
                        <th><nobr>CWE-ID</nobr></th>
                        <th>弱點名稱</th>
                        <th>來源</th>
                    </tr>
                    </thead>
                    <tbody>
                                <tr>
                                    <td><nobr><a href="/zh-hant/cwe/cwe-79.html">CWE-79</a></nobr></td>
                                    <td><b>Improper Neutralization of Input During Web Page Generation</b><br>The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.</td>
                                    <td></td>
                                </tr>
                </tbody>
            </table>
        </div>
            <div class="separator my-10"></div>

<div class="table-responsive">
                <table class="table table-striped gy-7 gs-7">
                    <thead>
                    <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
                        <th>指標</th>
                        <th>評分</th>
                        <th>嚴重程度</th>
                        <th>CVSS 向量</th>
                        <th>來源</th>
                    </tr>
                    </thead>
                    <tbody>
                <tr>
                    <td>V3.0</td>
                    <td>5.4</td>
                    <td>MEDIUM</td>
                    <td>
                        CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N                                <div class="m-0">
            <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-179432563814411" aria-expanded="false">
                <div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
                    <i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                    </i>
                    <i class="ki-duotone ki-plus-square toggle-off fs-4">
                        <span class="path1"></span>
                        <span class="path2"></span>
                        <span class="path3"></span>
                    </i>
                </div>
                <span class="text-gray-700 cursor-pointer mb-0">更多資訊</span>
            </div>
            <div id="metric-179432563814411" class="fs-7 ms-1 collapse" style="">
                <div class="mb-4">
                    <div class="d-flex align-items-center ps-10 mb-n1">
                        <div class="text-gray-600 fs-7">
                            <h4 class='bg-light border border-gray-300 rounded p-2'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers). </p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Required</p></div><div style='flex: 1;margin-left:5px;'><p>Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Scope Metrics</h4><p>An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges. </p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Changed</p></div><div style='flex: 1;margin-left:5px;'><p>	An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Impact Metrics</h4><p>The Impact metrics refer to the properties of the impacted component. </p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the impacted component.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Temporal Metrics</h4><p>The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.</p><h4 class='bg-light border border-gray-300 rounded p-2'>Environmental Metrics</h4><p></p>                        </div>
                    </div>
                </div>
            </div>
        </div>
                    </td>
                    <td>nvd@nist.gov</td>
                </tr>
                    <tr>
                        <td>V2</td>
                        <td>3.5</td>
                        <td></td>
                        <td>
                            AV:N/AC:M/Au:S/C:N/I:P/A:N                        </td>
                        <td>nvd@nist.gov</td>
                    </tr>
                </tbody>
            </table>
        </div>
            <div class="separator my-10"></div>

<h2>EPSS</h2>
            <div class="mb-4">EPSS 是一種預測漏洞被利用可能性的評分模型。</div>

<h3>EPSS 評分</h3>
            <div>EPSS 模型產生介於 0 到 1（0% 到 100%）之間的概率分數。分數越高，漏洞被利用的概率越大。</div>
            <div id="chartEpss"></div>

<h3>EPSS 百分位數</h3>
            <div>百分位數用於根據 EPSS 分數對 CVE 進行排名。例如，EPSS 評分在第 95 百分位的 CVE 比 95% 的其他 CVE 更有可能被利用。因此，百分位數用於比較某 CVE 的 EPSS 分數與其他 CVE 的相對位置。</div>
            <div id="chartPercentile"></div>
            <div class="text-center">
                <a href="https://www.first.org/epss/" target="_parent">EPSS First.org<i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a>
            </div>

};
            </script>

<h2 class="tw-h3">相關產品</h2>
<h3 class='tw-h4'>設定 0</h3><p>I4a>>Donlinkage >> Version 6.6.8</p>            <div class="separator my-10"></div>

<h2 class='tw-h3'>參考資料</h2><div style='margin-bottom: 10px;'><a href='http://www.safecomp.com/blog/donlinkage.html' target='_blank'>http://www.safecomp.com/blog/donlinkage.html <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : x_refsource_MISC</span></div><div class="separator my-10"></div>                            </div>
                        </div>

</div>
                </div>
            </div>
        </div>
        
 
                    
                            <div class="footer py-4 d-flex flex-lg-column" id="kt_footer">
            <div class="container-xxl d-flex flex-column flex-md-row align-items-center justify-content-between">
                <div class="text-gray-900 order-2 order-md-1">
                    <span class="text-muted fw-semibold me-1">2026©</span>
                    <a href="https://www.tesweb.com" target="_blank" class="text-gray-800 text-hover-primary">tesweb SA</a>,
                    <a href="https://www.bexxo.ch" target="_blank" class="text-gray-800 text-hover-primary">bexxo Cyber Security</a>
                </div>
                <ul class="menu menu-gray-600 menu-hover-primary fw-semibold order-1">

<li class="menu-item">
                        <a href="/zh-hant/official.html" class="menu-link px-2">資料來源</a>
                    </li>
                    <li class="menu-item">
                        <a href="/zh-hant/gdpr.html" class="menu-link px-2">GDPR</a>
                    </li>
                    <li class="menu-item">
                        <a href="#" id="gdpr-manage-cookies" class="menu-link px-2">管理 Cookie</a>
                    </li>
                    <li class="menu-item">
                        <a href="/zh-hant/contact.html" class="menu-link px-2">聯絡</a>
                    </li>
                    <li class="menu-item">
                        <a href="/zh-hant/plan-price.html" class="menu-link px-2">購買</a>
                    </li>
                    <li class="menu-item">
                        <a href="https://www.linkedin.com/company/cve-find/" class="menu-link px-2" target="_blank"><img src="/media/social/linkedin.svg" width="40" height="40" alt="LinkedIn Account"/></a>
                    </li>
                    <li class="menu-item">
                        <a href="https://www.facebook.com/people/CVE-Find-Alert/61561116452093/" class="menu-link px-2" target="_blank"><img src="/media/social/facebook.svg" width="40" height="40" alt="Facebook Account"/></a>
                    </li>
                    <li class="menu-item">
                        <a href="https://x.com/cvefindcom" class="menu-link px-2" target="_blank"><img src="/media/social/twitter.svg" width="40" height="40" alt="Twitter Account"/></a>
                    </li>
                </ul>
            </div>
        </div>
        <div class="footer py-4">
            <div class="container-xxl align-items-center justify-content-between">
                cvefind.com 上呈現的資訊來自多個精心挑選的參考來源。CVE 資料由 <a href="https://cve.mitre.org/" target="_blank">MITRE Corporation</a> 和 <a href="https://nvd.nist.gov/" target="_blank">國家漏洞資料庫（NVD）</a>提供。已知被利用漏洞（KEV）目錄來自 <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" target="_blank">網路安全暨基礎設施安全局（CISA）</a>，而 EPSS 評分來自 <a href="https://www.first.org/epss/" target="_blank">FIRST.org</a>。此外，軟體弱點（CWE）和常見攻擊模式（CAPEC）的資料由 <a href="https://mitre.org/" target="_blank">MITRE Corporation</a> 維護，硬軟體配置（CPE）資訊由 <a href="https://nvd.nist.gov/products/cpe" target="_blank">NVD</a> 提供。            </div>
        </div>

</div>
            </div>
        </div>

<script>var hostUrl = "assets/";</script>
                <script src="/plugins/global/plugins.bundle.min.1743008562.js"></script>
                <script src="/js/scripts.bundle.1718974735.js"></script>

<div class="ea-slot d-lg-none" data-ea-anchor="mobile" data-ea-pub="cvefindcom" data-ea-type="text" data-ea-style="fixedfooter" data-ea-kw="security|cybersecurity|vulnerability|cve"></div>                    <style>
                        /* Encart EthicalAds centré dans son emplacement */
                        .ea-slot [data-ea-publisher]{margin-left:auto;margin-right:auto;}
                        /* Format horizontal : remplit la largeur de la colonne (variable officielle EthicalAds) */
                        .ea-slot [data-ea-publisher].horizontal{--ea-image-placement-width-horizontal:100%;}
                    </style>
                    <script async src="https://media.ethicalads.io/media/client/ethicalads.min.js"></script>
                    <script src="/js/app/ads/ethicalads.min.1792667231.js" defer></script>
                            </body>
        </html>
<script>
var cookieTimezoneBrowser = function () {
    let timeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;

var offset = -new Date().getTimezoneOffset();
    var prefix = offset >= 0 ? '+' : '-';
    var timezoneOffset = prefix + Math.floor(Math.abs(offset) / 60).toString().padStart(2, '0') + ':' + (Math.abs(offset) % 60).toString().padStart(2, '0');

document.cookie = "tw-browser=" + timeZone+"|"+ timezoneOffset+ "; path=/";
}
cookieTimezoneBrowser();
</script>

CVE-2018-17090：詳細資料

CVE 描述