Skip to main content

CVE-1999-1055: Microsoft Excel 97 does not warn the user before executing worksheet functions, which could allow at

High
VulnerabilityCVE-1999-1055cve-1999-1055
Published: Fri Dec 31 1999 (12/31/1999, 05:00:00 UTC)
Source: NVD
Vendor/Project: microsoft
Product: excel

Description

Microsoft Excel 97 does not warn the user before executing worksheet functions, which could allow attackers to execute arbitrary commands by using the CALL function to execute a malicious DLL, aka the Excel "CALL Vulnerability."

AI-Powered Analysis

AILast updated: 06/25/2025, 17:21:09 UTC

Technical Analysis

CVE-1999-1055 is a high-severity vulnerability affecting Microsoft Excel 97, identified as the "Excel CALL Vulnerability." The core issue arises because Excel 97 does not prompt or warn users before executing worksheet functions, specifically the CALL function. This function can be exploited by attackers to execute arbitrary commands by invoking a malicious Dynamic Link Library (DLL). Essentially, an attacker can craft an Excel spreadsheet containing a CALL function that references a malicious DLL. When the spreadsheet is opened, Excel executes the CALL function without any user confirmation, leading to the execution of arbitrary code on the victim's system. This vulnerability impacts the confidentiality, integrity, and availability of the affected system, as arbitrary code execution can lead to data theft, system compromise, or denial of service. The vulnerability is remotely exploitable without authentication (AV:N/AC:L/Au:N), meaning an attacker can deliver a malicious Excel file via email or other means and trigger the exploit simply by the user opening the file. The CVSS score of 7.5 reflects the high risk posed by this vulnerability. Although this vulnerability was disclosed in 1999 and patches were made available (MS98-018), many legacy systems or organizations using outdated software might still be vulnerable. No known exploits in the wild have been reported recently, but the potential for exploitation remains, especially in environments where legacy Excel 97 files are still in use. The vulnerability highlights the risk of executing embedded functions without user consent and the importance of patching and updating software to mitigate such risks.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, particularly for entities still reliant on legacy systems or older versions of Microsoft Office. Exploitation could lead to unauthorized code execution, resulting in data breaches, intellectual property theft, or disruption of business operations. Sectors such as finance, government, and critical infrastructure that often handle sensitive data and may have legacy systems in place could face heightened risks. The ability to execute arbitrary code without user interaction increases the threat level, as attackers can deliver malicious Excel files via phishing campaigns or supply chain attacks. This could lead to widespread compromise if malicious documents are distributed internally or externally. Additionally, compromised systems could be used as footholds for lateral movement within networks, escalating the severity of the breach. While modern versions of Excel have mitigations and warnings, organizations with legacy dependencies must be particularly vigilant. The lack of recent known exploits suggests limited active targeting, but the potential impact remains high if exploited.

Mitigation Recommendations

1. Immediate patching: Apply the security update MS98-018 or later patches that address this vulnerability. Even though the vulnerability is old, ensuring all legacy systems are updated is critical. 2. Upgrade software: Migrate from Microsoft Excel 97 to supported, modern versions of Microsoft Office that include enhanced security features and user prompts for executing embedded functions. 3. Email filtering and attachment controls: Implement advanced email security solutions that scan and block potentially malicious Excel files, especially those containing macros or embedded functions like CALL. 4. User awareness training: Educate users about the risks of opening unsolicited or unexpected Excel files, emphasizing caution with legacy file formats. 5. Application whitelisting: Use application control solutions to restrict execution of unauthorized DLLs or scripts, limiting the ability of malicious code to run even if the file is opened. 6. Network segmentation: Isolate legacy systems to reduce the risk of lateral movement if a compromise occurs. 7. Disable or restrict the CALL function if possible through group policies or Excel settings, to prevent execution of external DLLs from spreadsheets. 8. Monitor and audit: Implement monitoring to detect unusual execution of Excel or DLL loading activities, enabling rapid detection of exploitation attempts.

Need more detailed analysis?Get Pro

Threat ID: 682ca32cb6fd31d6ed7df5c6

Added to database: 5/20/2025, 3:43:40 PM

Last enriched: 6/25/2025, 5:21:09 PM

Last updated: 8/15/2025, 5:58:40 AM

Views: 11

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats