CVE-2007-0028
What it is
Microsoft Excel 2000, 2002, 2003, Viewer 2003, Office 2004 for Mac, and Office v.X for Mac does not properly handle certain opcodes, which allows user-assisted remote attackers to execute arbitrary code via a crafted XLS file, which results in an "Improper Memory Access Vulnerability." NOTE: an early disclosure of this issue used CVE-2006-3432, but only CVE-2007-0028 should be used.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 33.9% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 33.9% in the next 30 days (EPSS).
- Severity: 9.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 33.9% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- Microsoft Excel 2000
- Microsoft Office 2000
- Microsoft Excel 2002
- Microsoft Office Xp
- Microsoft Excel 2003
- Microsoft Office 2003
- Microsoft Excel Viewer 2003
- Microsoft Works 2004
Attack profile CVSS 2.0 · 9.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
Raw vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2007-0028.md and follow it. Check whether this project is affected by CVE-2007-0028. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://secunia.com/advisories/23676
- http://www.kb.cert.org/vuls/id/493185
- http://www.vupen.com/english/advisories/2007/0103
- http://secunia.com/advisories/23676
- http://www.kb.cert.org/vuls/id/493185
- http://www.vupen.com/english/advisories/2007/0103
References
- http://secunia.com/advisories/23676
- http://securitytracker.com/id?1017485
- http://www.fortinet.com/FortiGuardCenter/advisory/FG-2006-30.html
- http://www.fortinet.com/FortiGuardCenter/advisory/FGA-2007-01.html
- http://www.kb.cert.org/vuls/id/493185
- http://www.osvdb.org/31249
- http://www.securityfocus.com/archive/1/457274/100/0/threaded
- http://www.securityfocus.com/bid/21952
- http://www.us-cert.gov/cas/techalerts/TA07-009A.html
- http://www.vupen.com/english/advisories/2007/0103
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-002
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A768
- http://secunia.com/advisories/23676
- http://securitytracker.com/id?1017485
- http://www.fortinet.com/FortiGuardCenter/advisory/FG-2006-30.html
- http://www.fortinet.com/FortiGuardCenter/advisory/FGA-2007-01.html
- http://www.kb.cert.org/vuls/id/493185
- http://www.osvdb.org/31249
- http://www.securityfocus.com/archive/1/457274/100/0/threaded
- http://www.securityfocus.com/bid/21952
- http://www.us-cert.gov/cas/techalerts/TA07-009A.html
- http://www.vupen.com/english/advisories/2007/0103
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-002
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A768