
Security News
/Research
Wallet-Draining npm Package Impersonates Nodemailer to Hijack Crypto Transactions
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
update-soap-server
Advanced tools
Soap server, using pure javascript for node.js.
var soap = require('soap-server');
function MyTestService(){
}
MyTestService.prototype.test1 = function(myArg1, myArg2){
return myArg1 + myArg2;
};
var soapServer = new soap.SoapServer();
var soapService = soapServer.addService('testService', new MyTestService());
soapServer.listen(1337, '127.0.0.1');
The WSDL at http://127.0.0.1:1337/testService?wsdl would be:
<?xml version="1.0"?>
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:tns="http://server.soap.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.soap.com/" name="testServiceService">
<types>
<xsd:schema version="1.0" targetNamespace="http://server.soap.com/">
<xsd:element name="MyObject" type="tns:MyObject"/>
<xsd:complexType name="MyObject">
<xsd:sequence>
<xsd:element name="concated" type="xsd:string" minOccurs="0"/>
<xsd:element name="incremented" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MyTestObject" type="tns:MyTestObject"/>
<xsd:complexType name="MyTestObject">
<xsd:sequence>
<xsd:element name="strArg" type="xsd:string" minOccurs="0"/>
<xsd:element name="intArg" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="test1">
<part name="myArg1" element="xsd:string"/>
<part name="myArg2" element="xsd:string"/>
</message>
<message name="test1Response">
<part name="return" element="xsd:string"/>
</message>
<portType name="testService">
<operation name="test1">
<input wsam:Action="test1" message="tns:test1"/>
<output wsam:Action="http://server.soap.com/testService/test1Response" message="tns:test1Response"/>
</operation>
</portType>
<binding name="testServicePortBinding" type="tns:testService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="test1">
<soap:operation soapAction="test1"/>
<input name="test1">
<soap:body use="literal"/>
</input>
<output name="test1Response">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="testServiceService">
<port name="testServicePort" binding="tns:testServicePortBinding">
<soap:address location="http://127.0.0.1:1337/testService"/>
</port>
</service>
</definitions>
function MyTestService(){
}
MyTestService.prototype.test2 = function(myArg1, myArg2){
return myArg1 + myArg2;
};
var soapServer = new soap.SoapServer();
var soapService = soapServer.addService('testService', new MyTestService());
var test2operation = soapService.getOperation('test2');
test2operation.setOutputType('number');
test2operation.setInputType('myArg1', {type: 'number'});
test2operation.setInputType('myArg2', {type: 'number'});
soapServer.listen(1337, '127.0.0.1');
The WSDL at http://127.0.0.1:1337/testService?wsdl would be:
<?xml version="1.0"?>
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:tns="http://server.soap.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.soap.com/" name="testServiceService">
<types>
<xsd:schema version="1.0" targetNamespace="http://server.soap.com/">
<xsd:element name="MyObject" type="tns:MyObject"/>
<xsd:complexType name="MyObject">
<xsd:sequence>
<xsd:element name="concated" type="xsd:string" minOccurs="0"/>
<xsd:element name="incremented" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MyTestObject" type="tns:MyTestObject"/>
<xsd:complexType name="MyTestObject">
<xsd:sequence>
<xsd:element name="strArg" type="xsd:string" minOccurs="0"/>
<xsd:element name="intArg" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="test2">
<part name="myArg1" element="xsd:int"/>
<part name="myArg2" element="xsd:int"/>
</message>
<message name="test2Response">
<part name="return" element="xsd:int"/>
</message>
<portType name="testService">
<operation name="test2">
<input wsam:Action="test2" message="tns:test2"/>
<output wsam:Action="http://server.soap.com/testService/test2Response" message="tns:test2Response"/>
</operation>
</portType>
<binding name="testServicePortBinding" type="tns:testService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="test2">
<soap:operation soapAction="test2"/>
<input name="test2">
<soap:body use="literal"/>
</input>
<output name="test2Response">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="testServiceService">
<port name="testServicePort" binding="tns:testServicePortBinding">
<soap:address location="http://127.0.0.1:1337/testService"/>
</port>
</service>
</definitions>
function MyObject(){
}
MyObject.prototype.concated = '';
MyObject.prototype.incremented = 0;
function MyTestService(){
}
MyTestService.prototype.test3 = function(strArg, intArg){
var ret = new MyObject();
ret.concated = strArg + '[' + intArg + ']';
ret.incremented = intArg + 1;
return ret;
};
var soapServer = new soap.SoapServer();
var soapService = soapServer.addService('testService', new MyTestService());
var test3operation = soapService.getOperation('test3');
test3operation.setOutputType(MyObject, 'MyObject');
test3operation.setInputType('intArg', {type: 'number'});
soapServer.listen(1337, '127.0.0.1');
The WSDL at http://127.0.0.1:1337/testService?wsdl would be:
<?xml version="1.0"?>
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:tns="http://server.soap.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.soap.com/" name="testServiceService">
<types>
<xsd:schema version="1.0" targetNamespace="http://server.soap.com/">
<xsd:element name="MyObject" type="tns:MyObject"/>
<xsd:complexType name="MyObject">
<xsd:sequence>
<xsd:element name="concated" type="xsd:string" minOccurs="0"/>
<xsd:element name="incremented" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MyTestObject" type="tns:MyTestObject"/>
<xsd:complexType name="MyTestObject">
<xsd:sequence>
<xsd:element name="strArg" type="xsd:string" minOccurs="0"/>
<xsd:element name="intArg" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="test2Response">
<part name="return" element="xsd:int"/>
</message>
<message name="test3">
<part name="strArg" element="xsd:string"/>
<part name="intArg" element="xsd:int"/>
</message>
<message name="test3Response">
<part name="return" element="tns:MyObject"/>
</messag
<portType name="testService">
<operation name="test3">
<input wsam:Action="test3" message="tns:test3"/>
<output wsam:Action="http://server.soap.com/testService/test3Response" message="tns:test3Response"/>
</operation>
</portType>
<binding name="testServicePortBinding" type="tns:testService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="test3">
<soap:operation soapAction="test3"/>
<input name="test3">
<soap:body use="literal"/>
</input>
<output name="test3Response">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="testServiceService">
<port name="testServicePort" binding="tns:testServicePortBinding">
<soap:address location="http://127.0.0.1:1337/testService"/>
</port>
</service>
</definitions>
function MyTestObject(){
}
MyTestObject.prototype.strArg = '';
MyTestObject.prototype.intArg = 0;
function MyTestService(){
}
MyTestService.prototype.test4 = function(myTestObjectInstance){
return myTestObjectInstance.strArg + '[' + myTestObjectInstance.intArg + ']';
};
var soapServer = new soap.SoapServer();
var soapService = soapServer.addService('testService', new MyTestService());
var test4operation = soapService.getOperation('test4');
test4operation.setInputType('myTestObjectInstance', MyTestObject);
soapServer.listen(1337, '127.0.0.1');
The WSDL at http://127.0.0.1:1337/testService?wsdl would be:
<?xml version="1.0"?>
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:tns="http://server.soap.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.soap.com/" name="testServiceService">
<types>
<xsd:schema version="1.0" targetNamespace="http://server.soap.com/">
<xsd:element name="MyObject" type="tns:MyObject"/>
<xsd:complexType name="MyObject">
<xsd:sequence>
<xsd:element name="concated" type="xsd:string" minOccurs="0"/>
<xsd:element name="incremented" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MyTestObject" type="tns:MyTestObject"/>
<xsd:complexType name="MyTestObject">
<xsd:sequence>
<xsd:element name="strArg" type="xsd:string" minOccurs="0"/>
<xsd:element name="intArg" type="xsd:int" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="test4">
<part name="myTestObjectInstance" element="tns:MyTestObject"/>
</message>
<message name="test4Response">
<part name="return" element="xsd:string"/>
</message>
<portType name="testService">
<operation name="test4">
<input wsam:Action="test4" message="tns:test4"/>
<output wsam:Action="http://server.soap.com/testService/test4Response" message="tns:test4Response"/>
</operation>
</portType>
<binding name="testServicePortBinding" type="tns:testService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="test4">
<soap:operation soapAction="test4"/>
<input name="test4">
<soap:body use="literal"/>
</input>
<output name="test4Response">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="testServiceService">
<port name="testServicePort" binding="tns:testServicePortBinding">
<soap:address location="http://127.0.0.1:1337/testService"/>
</port>
</service>
</definitions>
FAQs
Soap server, using pure javascript.
The npm package update-soap-server receives a total of 0 weekly downloads. As such, update-soap-server popularity was classified as not popular.
We found that update-soap-server demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.