IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 229714.

**Security Bulletin**

  

**Summary**

IBM WebSphere Application Server is vulnerable to cross-site scripting in the Admin Console. This has been addressed.

**Vulnerability Details**

**CVEID:**   CVE-2022-34336  
**DESCRIPTION:**   IBM WebSphere Application Server is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.  
CVSS Base score: 5.4  
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/229714 for the current score.  
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)

**Affected Products and Versions**

Affected Product(s)

Version(s)

IBM WebSphere Application Server

9.0

IBM WebSphere Application Server

8.5

IBM WebSphere Application Server

8.0

IBM WebSphere Application Server

7.0

**Remediation/Fixes**

 IBM strongly recommends addressing the vulnerability now by applying a currently available interim fix or fix pack that contains the APAR PH47531.

**For IBM WebSphere Application Server traditional:**

**For V9.0.0.0 through 9.0.5.13:**  
· Upgrade to minimal fix pack levels as required by interim fix and then apply Interim Fix  PH47531  
\--OR--  
· Apply Fix Pack 9.0.5.14 or later (targeted availability 4Q2022). 

**For V8.5.0.0 through 8.5.5.22:**  
· Upgrade to minimal fix pack levels as required by interim fix and then apply Interim Fix PH47531  
\--OR--  
· Apply Fix Pack 8.5.5.23 or later (targeted availability 1Q2023). 

**For V8.0.0.0 through 8.0.0.15:**  
· Upgrade to 8.0.0.15 and then apply Interim Fix PH47531  
 

**For V7.0.0.0 through 7.0.0.45:**  
· Upgrade to 7.0.0.45 and  then apply Interim Fix PH47531  
 

Additional interim fixes may be available and linked off the interim fix download page.

_IBM WebSphere Application Server V7.0 and V8.0 are no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product._

**Workarounds and Mitigations**

None

**References**

Off

**Change History**

12 Sep 2022: Initial Publication

\*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

**Disclaimer**

According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.

**Document Location**

Worldwide

\[{"Business Unit":{"code":"BU059","label":"IBM Software w\\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","Platform":\[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\\/OS"}\],"Version":"7.0, 8.0, 8.5, 9.0","Edition":"Advanced,Base,Developer,Enterprise,Express,Network Deployment,Single Server","Line of Business":{"code":"LOB45","label":"Automation"}}\]

CVE-2022-34336: IBM WebSphere Application Server is vulnerable to cross-site scripting in the Admin Console (CVE-2022-34336)

In Amanda 3.5.1, an information leak vulnerability was found in the calcsize SUID binary. An attacker can abuse this vulnerability to know if a directory exists or not anywhere in the fs. The binary will use `opendir()` as root directly without checking the path, letting the attacker provide an arbitrary path.

**What is Amanda?**

AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup solution that allows the IT administrator to set up a single master backup server to back up multiple hosts over network to tape drives/changers or disks or optical media. Amanda uses native utilities and formats (e.g. dump and/or GNU tar) and can back up a large number of servers and workstations running multiple versions of Linux or Unix. Amanda uses a native Windows client to back up Microsoft Windows desktops and servers.

The **latest stable version of Amanda**, 3.5.2 was released on 20th July 2022. As part of this release, we have addressed unintentional deletions of tape data in the backup environment. Your existing data on tapes will be safe and will not get replaced by your new backup set.

The most recent **stable release** is version 3.5.1, released on December 1, 2017.

The latest **release** is the 3.4.x series is 3.4,5, released on June 8, 2017. This is a bugfix release for 3.4.4.  

The latest **release** is the 3.3.x series is 3.3.9, released on February 10, 2016. It is a security fix. The amanda user was allowed to run any code as root, upgrade is not required if you trust the amanda user.

The latest **release** in the 3.2.x series is 3.2.3, released on May 9, 2011. It is a bug fix release for version 3.2.2.

The latest **release** in the 3.1.x series is 3.1.3, released on October 5, 2010. It is a security release for version 3.1.2.

Amanda-3.1.2 has a known security vulnerability, and all users should upgrade to Amanda-3.1.3 as soon as possible. See the security alert.

**Download here!** (README) | Learn more about Amanda's 3.5.2 release in our blog

**Release Notes for 3.5.2:**

The 3.5.2 version of Amanda will prevent unintentional deletions of data on tapes. With this release, you can stay assured that your data on tapes is safe, irrespective of the value set on the retention period.

**Enhancement**

Prevent auto-label from erasing tapes - Auto-label is disabled from claiming non-Amanda and other configuration labels by default. This change will prevent rewriting your existing tape media with new backup set.

**Release Notes for 3.5.1:**

*   compilation on Solaris
*   Do not check all 'r' bit on suid binary
*   Fix parsing of configuration override (-o)

*   can unset some setting

*   client code will not fail if shared memory is not available
*   amreport

*   lot of improvement

*   allow '\*' for a datestamp wildcard
*   amgetconf

*   print an empty string if a parameter is not set instead of 'no such parameter'

*   amdump

*   new --no-dump, --no-flush and --no-vault argument

*   amstatus fix
*   lock holding disk to protect multiple parallel access

**Release Notes for 3.5:**

*   Use different thread to connect to different client
*   amservice, amcheck, planner, dumper are no longer suid root
*   ambind

*   new suid program to bind to a privileged port

*   amanda-security.conf

*   new tcp\_port\_range, range of privileged tcp port
*   new udp\_port\_range, range of privileged udp port

*   S3 device

*   openstack keystone v3 support

*   device-property STORAGE-API must be set to SWIFT-3
*   new PROJECT-NAME device-property
*   new DOMAIN-NAME device-property

*   amfetchdump

*   rename --directory argument to --target

*   ampgsql

*   new --incremental property
*   new --remove-full-wal property
*   new --remove-incremental-wal property

  
*   fix planner looping
*   fix overflow in S3 device
*   fix compilation on OpenBSD
*   fix race in amarchive reader
*   fix amflush (flush date selected by user)
*   fix local auth, use getaddrinfo to find if the host is local
*   fix dumper cancelling the shm\_ring with a STRANGE result
*   fix chunker hang
*   Improve taperscan with chg-single and interactivity

**View more available versions**

**Amanda Web Pages**

*   Amanda wiki
*   **Backup & Recovery** (O'Reilly 2007) has a chapter dedicated to Amanda.

  
_Last updated: $Date: 2017-09-28 21:37:44 $_

CVE-2022-37703: Open Source Backup for Linux, Windows, UNIX and OS X

Cyber spies are using legitimate apps for DLL sideloading, deploying an updated range of malware, including the new "Logdatter" info-stealer.

A threat group previously associated with the notorious ShadowPad remote access Trojan (RAT) has been observed using old and outdated versions of popular software packages to load malware on systems belonging to multiple target government and defense organizations in Asia.

The reason for using outdated versions of legitimate software is because they allow the attackers to use a well-known method called dynamic link library (DLL) sideloading to execute their malicious payloads on a target system. Most current versions of the same products protect against the attack vector, which basically involves adversaries disguising a malicious DLL file as a legitimate one and putting it in a directory where the application would automatically load and run the file.

Researchers from Broadcom's Software's Symantec Threat Hunter team observed the ShadowPad\-related threat group using the tactic in a cyber-espionage campaign. The group's targets have so far included a prime minister's office, government organizations linked to the finance sector, government-owned defense and aerospace firms, and state-owned telecom, IT, and media companies. The security vendor's analysis showed the campaign has been ongoing since at least early 2021, with intelligence being the primary focus.

**A Well-Known Cyberattack Tactic, but Successful**

"The use of legitimate applications to facilitate DLL sideloading appears to be a growing trend among espionage actors operating in the region," Symantec said in a report this week. It's an attractive tactic because anti-malware tools often don't spot the malicious activity because attackers used old applications for side loading.

"Aside from the age of the applications, the other commonality is that they were all relatively well-known names and thus may appear innocuous." says Alan Neville, threat intelligence analyst with Symantec's threat hunter team.  

The fact that the group behind the current campaign in Asia is using the tactic despite it being well-understood suggests the technique is yielding some success, Symantec said.

Neville says his company has not recently observed threat actors use the tactic in the US or elsewhere. "The technique is mostly used by attackers focusing on Asian organizations," he adds.

Neville says that in most of the attacks in the latest campaign, threat actors used the legitimate PsExec Windows utility for executing programs on remote systems to carry out the sideloading and deploy malware. In each case, the attackers had already previously compromised the systems on which it installed the old, legitimate apps.

"\[The programs\] were installed on each compromised computer the attackers wanted to run malware on. In some cases, it could be multiple computers on the same victim network," Neville says. In other instances, Symantec also observed them deploying multiple legitimate application on a single machine to load their malware, he adds.

"They used quite an array of software, including security software, graphics software, and Web browsers," he notes. In some cases, Symantec researchers also observed the attacker using legitimate system files from the legacy Windows XP OS to enable the attack.  

**Logdatter, Range of Malicious Payloads**

One of the malicious payloads is a new information stealer dubbed Logdatter, which allows the attackers to log keystrokes, take screenshots, query SQL databases, inject arbitrary code, and download files, among other things. Other payloads that the threat actor is using in its Asian campaign include a PlugX-based Trojan, two RATs dubbed Trochilus and Quasar, and several legitimate dual-use tools. These include Ladon, a penetration testing framework, FScan, and NBTscan for scanning victim environments.

Neville says Symantec has been unable to determine with certainty how the threat actors might be gaining initial access on a target environment. But phishing and opportunity targeting of unpatched systems are likely vectors.

"Alternatively, a software supply chain attack is not outside the remit of these attackers as actors with access to ShadowPad are known to have launched supply chain attacks in the past," Neville notes. Once the threat actors have gained access to an environment, they have tended to use a range of scanning tools such as NBTScan, TCPing, FastReverseProxy, and Fscan to look for other systems to target.

To defend against these kinds of attacks, organizations need to implement mechanisms for auditing and controlling what software might be running on their network. They should also consider implementing a policy of only allowing whitelisted applications to run in the environment and prioritize patching of vulnerabilities in public-facing applications. 

"We'd also recommend taking immediate action to clean machines that exhibit any indicators of compromise," Neville advises, "... including cycling credentials and following your own organization's internal process to perform a thorough investigation."

ShadowPad Threat Actors Return With Fresh Government Strikes, Updated Tools

Windows Kernel Elevation of Privilege Vulnerability. This CVE ID is unique from CVE-2022-37956, CVE-2022-37957.

CVE-2022-37964

Windows DNS Server Denial of Service Vulnerability.

CVE-2022-34724

Windows DPAPI (Data Protection Application Programming Interface) Information Disclosure Vulnerability.

CVE-2022-34723

Windows Kerberos Elevation of Privilege Vulnerability. This CVE ID is unique from CVE-2022-33647.

CVE-2022-33679

Windows Kerberos Elevation of Privilege Vulnerability. This CVE ID is unique from CVE-2022-33679.

CVE-2022-33647

Windows Secure Channel Denial of Service Vulnerability. This CVE ID is unique from CVE-2022-35833.

CVE-2022-30196

Windows ALPC Elevation of Privilege Vulnerability.

Tag

#windows